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
- Blackhat Hacker Tools
- Hacking Tools For Games
- Hacker Tools 2019
- Pentest Tools Nmap
- Hacker Tools Hardware
- World No 1 Hacker Software
- Hacker Tools Windows
- Pentest Tools Find Subdomains
- Hackers Toolbox
- Pentest Tools For Ubuntu
- Usb Pentest Tools
- Pentest Tools Linux
- Hacker Tools Apk
- Pentest Tools Kali Linux
- Hacking App
- Pentest Tools Github
- Pentest Tools Website Vulnerability
- Pentest Tools For Mac
- Hacks And Tools
- Hacking Tools And Software
- Android Hack Tools Github
- What Are Hacking Tools
- Black Hat Hacker Tools
- Game Hacking
- Hack Tools Github
- Hacker Tools List
- World No 1 Hacker Software
- Hacking App
- Computer Hacker
- Pentest Tools List
- Hack Tools
- Hack Tools 2019
- Github Hacking Tools
- Pentest Tools Github
- Hacker Tools Github
- Best Hacking Tools 2019
- Hacking Tools For Kali Linux
- Hacker Tools Hardware
- Hacks And Tools
- Pentest Tools For Mac
- Hack Tools Github
- Hacking Tools For Beginners
- Pentest Box Tools Download
- Hacking Tools Online
- Best Hacking Tools 2020
- Pentest Tools Website
- Hacking Tools For Windows 7
- Pentest Tools Review
- Pentest Tools Github
- Pentest Tools List
- Hacking Tools For Games
- Black Hat Hacker Tools
- Hacking App
- Pentest Tools
- Hack Tool Apk
- Nsa Hack Tools Download
- Hacking Tools For Kali Linux
- New Hacker Tools
- Pentest Tools Subdomain
- Ethical Hacker Tools
- Hacking Tools For Games
- Hack Rom Tools
- Android Hack Tools Github
- Hack Tools Github
- Hacker Search Tools
- Hack And Tools
- Hacking Tools Name
- Hacking Tools 2019
- Hacker
- Hacker Tools Windows
- Hacking Tools Free Download
- Pentest Tools Url Fuzzer
- Hack Tools For Mac
- Best Pentesting Tools 2018
- World No 1 Hacker Software
- Hacker Tools Online
No comments:
Post a Comment