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
noorqureshi/reverse-eng-binary-triageReverse engineering e fuzzing

reverse-eng-binary-triage

⁨Triage a native binary you can run or read — find the vulnerable logic, the dangerous sinks, and the input path — with static + dynamic analysis. Load when handed an ELF/PE/Mach-O, a thick client, a standalone or obfuscated binary, or a service whose source you don't have. Signals: a compiled execut⁩

v2026.10.14-ee0e0c52 installazioni+2 in 7 giorni27 StelleMITsincronizzato 22 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reverse-eng-binary-triage

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

FirmaFirmato, ed25519
2BHcv4yrp8…vqO2QjAA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto4e285028…4103ef37
4e28502879e1…1e424103ef371 file · ⁦1.9 KB⁩
ScansioneBassonessuna segnalazione
La scansione non ha trovato nulla da segnalare in questa versione.Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-binary-triage@ee0e0c5

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

When it applies

You have a compiled binary — a thick desktop/mobile client, a network service, a setuid helper during privesc, or a firmware component (reverse-eng-firmware) — and no source. You need to understand what it does, where attacker input reaches, and whether that path is exploitable, before committing to exploit-poc-development.

Why it works

A binary carries its logic in the code and its intent in the strings, imports, and symbols. Cheap static passes (strings, imports, cross-references) point straight at the interesting functions; a debugger then confirms what actually happens at runtime, so you spend deep analysis only on the paths that matter.

Method

  1. Cheap recon first. file, strings -n8, and the import table tell you the language, protections, and intent in seconds. checksec (or rabin2 -I) for NX / PIE / RELRO / canary — they scope what an exploit would even need.
  2. Map input → sink. Find where input enters (recv, read, argv, getenv, a file/format parse) and trace to dangerous sinks: strcpy/memcpy/sprintf/gets (overflow), system/exec/popen (command injection), format-string sinks (printf(user)), and integer math feeding an allocation size.
  3. Read it in a decompiler. Ghidra or radare2/Cutter — jump to the sink, follow cross-references back to reachable entry points, and note the preconditions to reach it.
  4. Confirm dynamically. Run under gdb+GEF/pwndbg (or ltrace/strace), break at the sink, feed a marker input, and watch whether you control size/pointer/format. A crash you can steer (controlled $pc, overwritten pointer) is the confirmation.
  5. Pull the low-hanging intel — hardcoded secrets/keys (CWE-798), debug/backdoor paths, weak auth checks (a strcmp against a literal), and custom-protocol structure for later fuzzing.

Gotchas

  • Stripped binaries have no symbols — lean on strings, imports, and library-call signatures; name functions as you go so the map survives.
  • Packed/obfuscated (high entropy, tiny import table) → deobfuscate first (reverse-eng-deobfuscation).
  • A crash is not yet a bug worth reporting — determine control and impact before you claim it; validate with reporting-triage-validation.
  • Analyze untrusted binaries in an isolated VM — running an unknown executable is itself risky.

Verify success

You can state the input path, the vulnerable sink, the preconditions to reach it, and a runtime observation (controlled crash or a leaked secret) that proves it — a concrete lead for exploit development, not a guess from the disassembly.

References

Ghidra & radare2 documentation; pwndbg/GEF; the checksec protections model; CWE-121/787/798.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellNoNo
Usa la reteNoNo
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

La scansione non ha trovato nulla da segnalare in questa versione.

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

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c54e285028Firmata–

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