Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
noorqureshi/reverse-eng-ghidraIngeniería inversa y fuzzing

reverse-eng-ghidra

⁨Reverse engineer with Ghidra (GUI, headless, or ghidra-mcp) — decompile, cross-references, scripting — when there's no IDA license, for batch/CI decompilation, or as a free second opinion. Load for "decompile without IDA", bulk analysis of many samples, analyzeHeadless, Ghidra scripts (Jython/PyGhid⁩

v2026.10.14-ee0e0c53 instalaciones+3 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-ghidra

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
1Dak5Gfv7Z…+VlRH6Ag==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete0190672f…4172eb69
0190672f9448…d9a54172eb691 archivo · ⁦2.2 KB⁩
EscaneoMedio3 hallazgos
  • injection.no_confirmationSKILL.md:37
  • injection.no_confirmationSKILL.md:60
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-ghidra@ee0e0c5

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When it applies

You need decompiler-grade analysis of an in-scope binary (scope.txt / client-owned / your own sample — tradecraft-scope-roe) and there's no IDA license, or you need to process many samples in batch or CI. Also the right call when a conclusion from reverse-eng-ida or reverse-eng-radare2 deserves an independent cross-check with a different decompiler.

Why it works

Ghidra's P-code lifter gives one decompiler across dozens of architectures (x86/ARM/MIPS/PPC and obscure firmware targets IDA may not load well), and headless mode turns the whole import → analyze → decompile pipeline into a scriptable batch step — so bulk triage costs the same as single-file analysis.

Method

  1. Project, import, analyze. New project → import the file → run auto-analysis with the default analyzers. Record the language/compiler spec Ghidra picked and the base address — a wrong language guess (e.g. wrong ARM variant) silently produces garbage decompilation.
  2. Anchor on strings and imports. Search → For Strings, then right-click → References to find the code that uses an interesting string; double-click a function to decompile it. Same input → sink discipline as reverse-eng-binary-triage: record the import table before drawing conclusions.
  3. Read and annotate. Decompile window for logic; L to rename, ; for a comment, plate comments for function summaries. Rename/retype as you go — it compounds.
  4. Automate with scripts. Window → Script Manager for Jython (Python 2.7) scripts; for real Python 3 use PyGhidra, which bridges to CPython.
  5. Batch with headless when processing many files or running in CI:
    text
    analyzeHeadless /path/to/project Proj -import sample.bin -postScript ExportDecomp.py
    (analyzeHeadless lives in Ghidra's support/ dir — locate it on your install, don't guess paths.)
  6. MCP bridge (optional). If ghidra-mcp is configured, pull decompilations and xrefs through its tools — confirm the actual port from your own config (commonly 8765) rather than assuming.
  7. Hand off when static runs out — dynamic confirmation goes to gdb/Frida (reverse-eng-binary-triage step 4); patch diffing between two builds is ghidriff's job.

Gotchas

  • Wrong language/compiler spec on import → confident but wrong pseudocode; re-import with the correct variant if decompilation looks structurally impossible.
  • Default analyzers aren't always enough — for aggressive optimizations or unusual files, rerun analysis with more options enabled rather than accepting partial functions.
  • Jython is Python 2.7 — scripts written for modern Python silently fail; use PyGhidra for Python 3.
  • Large binaries are slow to analyze — scope analysis options, don't just wait and assume a hang.
  • Packed/obfuscated samples decompile to noise — unpack/deobfuscate first (reverse-eng-deobfuscation); don't read flattened junk as if it were logic.
  • Analyze untrusted binaries in an isolated VM.

Verify success

You can hand over named functions at concrete addresses with readable pseudocode for the key logic, plus reproducible steps (project/script/headless command) so a teammate gets the same result — or a headless run that emitted decompilations for every sample in the batch.

References

Ghidra docs (incl. the analyzeHeadless README); PyGhidra; ghidriff for patch diffing.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaPrompt injection · injection.no_confirmationSKILL.md:37
  2. MediaPrompt injection · injection.no_confirmationSKILL.md:60
  3. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.10.14-ee0e0c513 nov 2026ee0e0c50190672fFirmada–

Pregunta 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. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login