reverse-engineering-shellcode
Analyzes position-independent shellcode: disassembling raw bytes at the right
v1.0.02 instalações+2 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/reverse-engineering-shellcodeGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotef19f7a3e…2734c80f
f19f7a3e404a…34172734c80f4 arquivos · 3.5 KBVarreduraMédio2 achados
- Script executável junto com a skillscripts/analyst.py
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-shellcode@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When to Use
- You extracted a raw code blob (from a document, exploit, injected memory region, or beacon) with no PE/ELF headers.
- You need to determine the architecture, recover the API-resolution method, and understand what the shellcode does.
- You want to emulate the shellcode safely to recover staged payloads or C2.
Do not use a file-format parser on shellcode — there is no header. Treat it as a flat byte stream at a known base and disassemble/emulate.
Prerequisites
- Capstone (
pip install capstone) for disassembly; Unicorn (pip install unicorn) for emulation. - Knowledge of the likely architecture/bitness (x86 vs x64) and calling context.
Workflow
Step 1: Determine architecture and entry
Try disassembling as x86 and x64; the one that yields coherent instructions (and a sane prologue) is correct. Shellcode usually starts executing at offset 0.
python scripts/analyst.py disasm shellcode.bin --arch x64Step 2: Recognize API resolution
Windows shellcode typically walks the PEB to find kernel32, then resolves exports by hash:
mov rax, gs:[60h] ; PEB (x64) / mov eax, fs:[30h] (x86)
... traverse Ldr -> InMemoryOrderModuleList
... hash export names, compare to embedded constantsRecovered hash constants feed the API-hash resolver (see the obfuscation skill).
Step 3: Identify the technique
Look for egg hunters (searching memory for a tag), socket setup (reverse/bind shell), or a
download-and-exec stager (WinINet/WinHTTP resolution then a URL).
Step 4: Emulate to recover behavior
Emulate with Unicorn, hooking memory and (optionally) faking API calls, to observe the control flow and extract strings/URLs the static view hides:
python scripts/analyst.py emulate shellcode.bin --arch x64 --base 0x140000000Step 5: Extract IOCs and payload
Recover C2 URLs/hosts, embedded second stages, and the resolved API set for the report.
Validation
- The chosen architecture yields a coherent prologue and no garbage instruction stream.
- Recovered API hashes resolve to a sensible function set (LoadLibrary/GetProcAddress, network APIs).
- Emulation reaches the network/exec stage consistent with the static read.
Pitfalls
- Disassembling at the wrong bitness and chasing nonsense.
- Emulating without bounding execution, looping forever on unresolved calls.
- Ignoring self-modifying decoders — emulate through the decode stub to reach real code.
References
- See
references/api-reference.mdfor the disassembler and emulator wrapper. - Capstone and Unicorn (linked in frontmatter).
Arquivos desta versão
references/11.2 KB
- api-reference.md1.2 KB
scripts/13.2 KB
- analyst.py3.2 KB
- LICENSE340 B
- SKILL.md3.4 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | f19f7a3e | Assinada | – |
Mais de meltedinhex
Tudo deste publicador- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
Mais em Engenharia reversa e fuzzing
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login