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
Related links
- Easy Hack Tools
- How To Hack
- Pentest Tools
- Pentest Tools
- Pentest Tools For Android
- Pentest Tools Kali Linux
- Hacking Tools Kit
- Computer Hacker
- Hacker Tool Kit
- Hacker
- Hack Tool Apk
- Pentest Tools Framework
- Install Pentest Tools Ubuntu
- Hacker Tools
- Hack Tools
- Pentest Tools Url Fuzzer
- Android Hack Tools Github
- Hacker Search Tools
- Hacker Tools List
- Pentest Box Tools Download
- Hacks And Tools
- Pentest Tools Apk
- What Are Hacking Tools
- New Hack Tools
- Hack Apps
- Pentest Tools Apk
- How To Hack
- Hacker Tools Software
- How To Make Hacking Tools
- Hack Tools Online
- Hacking Tools Name
- Hack Tools For Ubuntu
- Hack Website Online Tool
- Hack Tools Github
- Hacking Tools For Pc
- Hacking Tools Mac
- Hack App
- New Hack Tools
- Pentest Tools Open Source
- Top Pentest Tools
- Pentest Tools Online
- Hacking Tools For Windows 7
- Hacker Techniques Tools And Incident Handling
- Pentest Recon Tools
- Pentest Tools
- Underground Hacker Sites
- Hak5 Tools
- Hacking Tools Windows 10
- Hacker Search Tools
- Usb Pentest Tools
- Hacking Tools For Games
- Pentest Tools Framework
- Hack Tools Github
- Pentest Tools Online
- Easy Hack Tools
- Pentest Tools For Ubuntu
- Hacker Tools Github
- Pentest Tools Android
- Best Hacking Tools 2019
- Hacker Search Tools
- Pentest Tools Review
- Hacker Tools For Windows
- Pentest Automation Tools
- Hack And Tools
- Tools For Hacker
- Beginner Hacker Tools
- Beginner Hacker Tools
- Nsa Hack Tools
- Hacker Tools Free Download
- Pentest Tools For Android
- Pentest Tools Website
- Hacking Tools Mac
- Hacker Security Tools
- Hack Apps
No hay comentarios:
Publicar un comentario