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 instalaciones+2 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/reverse-eng-binary-triageEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete4e285028…4103ef37
4e28502879e1…1e424103ef371 archivo · 1.9 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-binary-triage@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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
- Cheap recon first.
file,strings -n8, and the import table tell you the language, protections, and intent in seconds.checksec(orrabin2 -I) for NX / PIE / RELRO / canary — they scope what an exploit would even need. - 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. - 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.
- Confirm dynamically. Run under
gdb+GEF/pwndbg (orltrace/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. - Pull the low-hanging intel — hardcoded secrets/keys (
CWE-798), debug/backdoor paths, weak auth checks (astrcmpagainst 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.
Archivos de esta versión
- SKILL.md3.5 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 4e285028 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Ingeniería inversa y fuzzing
Ver la categoríaPregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login