BOF implementation of the research by @jonasLyk and the drafted PoC from @LloydLabs
I didn't see that it currently existed (via the Community Kit) at the time of authorship.
- In this case, you have two options:
- Use the existing, compiled object file, located in the
dist
directory (AKA proceed to major step two) - Compile from source via the
Makefile
cd src
make clean
make
- Use the existing, compiled object file, located in the
- Load the
Aggressor
file, in theScript Manager
, located in thedist
directory - Within a provided
Beacon
,beacon> self_delete
- We're still using the
Win32
API andDynamic Function Resolution
. This is for you to determine as far as "risk".- Most of these calls can be replaced with
Nt
orZw
equivalents, which most (if not all) relevant stubs have been generated for you in thesyscalls.h
header file.- I may replace these with the aforementioned at a later point, but as it stands, I just wanted this up and "out there" for people first and foremost.
- As it stands, there is one
64-bit
call toNtClose
, if you wish, you may just create theDynamic Function Resolution
prototype inwin32_api.h
forCloseHandle
.
- Most of these calls can be replaced with