And it now landed!
A PoC implementation of Thread Stack Spoofing being an advanced In-Memory evasion technique allowing to better hide injected shellcode's memory allocations from scanners and analysts.
Inspired by marvelous Nighthawk C2!
github.com/mgeeky/ThreadS
Conversation
Since the outcome is the same, resulting in a fake call stack - what's the deal whether the implementation is similar to the Nighthawk's one or not? Would you rather call it "Call Stack Spoofing" instead?
1
1
If you'd even just take a look at your own screenshot, you'd see every fake "frame" is 8 bytes - since CreateFileW is a leaf function. Also leafs may never call, your frames are misaligned, and your last frame unwind to an invalid rip, blatantly leaving non-unwound stack remainin


