Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/reverse-engineering-shellcodeReverse engineering e fuzzing

reverse-engineering-shellcode

⁨Analyzes position-independent shellcode: disassembling raw bytes at the right⁩

v1.0.02 installazioni+2 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/reverse-engineering-shellcode

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
5neJWpQ1ai…BNtDVvAw==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettof19f7a3e…2734c80f
f19f7a3e404a…34172734c80f4 file · ⁦3.5 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/reverse-engineering-shellcode@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

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.

bash
python scripts/analyst.py disasm shellcode.bin --arch x64

Step 2: Recognize API resolution

Windows shellcode typically walks the PEB to find kernel32, then resolves exports by hash:

text
mov rax, gs:[60h]        ; PEB (x64)   / mov eax, fs:[30h] (x86)
... traverse Ldr -> InMemoryOrderModuleList
... hash export names, compare to embedded constants

Recovered 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:

bash
python scripts/analyst.py emulate shellcode.bin --arch x64 --base 0x140000000

Step 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.md for the disassembler and emulator wrapper.
  • Capstone and Unicorn (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600af19f7a3eFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login