Lets check different Cobalt Strike shellcodes and stages in the shellcodes emulator SCEMU.
This stages are fully emulated well and can get the IOC and the behavior of the shellcode.
But lets see another first stage big shellcode with c runtime embedded in a second stage.
In this case is loading tons of API using GetProcAddress at the beginning, then some encode/decode pointer and tls get/set values to store an address. And ends up crashing because is jumping an address that seems more code than address 0x9090f1eb.
Here there are two types of allocations:
Lets spawn a console on -c 3307548 and see if some of this allocations has the next stage.
The "m" command show all the memory maps but the "ma" show only the allocations done by the shellcode.
Dumping memory with "md" we see that there is data, and dissasembling this address with "d" we see the prolog of a function.
So we have second stage unpacked in alloc_e40064
With "mdd" we do a memory dump to disk we found the size in previous screenshot, and we can do some static reversing of stage2 in radare/ghidra/ida
In radare we can verify that the extracted is the next stage:
I usually do correlation between the emulation and ghidra, to understand the algorithms.
If wee look further we can realize that the emulator called a function on the stage2, we can see the change of code base address and is calling the allocated buffer in 0x4f...
And this stage2 perform several API calls let's check it in ghidra.
We can see in the emulator that enters in the IF block, and what are the (*DAT_...)() calls
Before a crash lets continue to the SEH pointer, in this case is the way, and the exception routine checks IsDebuggerPresent() which is not any debugger pressent for sure, so eax = 0;
So lets say yes and continue the emulation.
Both IsDebuggerPresent() and UnHandledExceptionFilter() can be used to detect a debugger, but the emulator return what has to return to not be detected.
Nevertheless the shellcode detects something and terminates the process.
Lets trace the branches to understand the logic:
target/release/scemu -f shellcodes/unsuported_cs.bin -vv | egrep '(\*\*|j|cmp|test)'
Lets see from the console where is pointing the SEH chain item:
to be continued ...
https://github.com/sha0coder/scemu
- Hackers Toolbox
- Best Pentesting Tools 2018
- Pentest Tools Github
- Best Pentesting Tools 2018
- Pentest Tools For Mac
- Pentest Tools Windows
- Pentest Tools For Mac
- Hackrf Tools
- Hacking Tools For Windows
- Physical Pentest Tools
- Nsa Hacker Tools
- Hacker Search Tools
- Hacking Tools 2020
- Hacker Tools For Windows
- Hacking Tools Kit
- Hacker Tools Free
- Hacker Tools 2020
- Hacker Tools Hardware
- New Hack Tools
- Hacker Tools For Windows
- Pentest Tools Url Fuzzer
- Hacker Tools For Ios
- Pentest Tools
- Hack Apps
- Pentest Automation Tools
- Hacking Tools Pc
- Best Hacking Tools 2020
- Growth Hacker Tools
- Pentest Automation Tools
- Pentest Tools Subdomain
- Pentest Tools For Android
- Hack And Tools
- Hacks And Tools
- Easy Hack Tools
- How To Install Pentest Tools In Ubuntu
- Pentest Box Tools Download
- Hack Tools Online
- Hacking Tools Download
- Hacker Tools For Pc
- Pentest Tools List
- Hacking Tools 2020
- Hack Tools Github
- Top Pentest Tools
- Pentest Tools Tcp Port Scanner
- Nsa Hack Tools
- Hacking App
- Pentest Tools Kali Linux
- Hacking Tools For Mac
- Hack Tools For Pc
- Hacking Tools Software
- Hacker Tools For Pc
- Hacking Tools For Windows 7
- Hacking Tools For Windows
- Hacking Tools For Pc
- Pentest Tools Free
- Ethical Hacker Tools
- Pentest Tools Windows
Tidak ada komentar:
Posting Komentar