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-binary-ninjaIngeniería inversa y fuzzing

reverse-eng-binary-ninja

⁨Reverse engineer in Binary Ninja — HLIL/MLIL/LLIL inspection, strings/imports/exports, cross-references, types, patching, Python API automation, and the optional MCP/HTTP bridge. Load when the user picks Binary Ninja, when its IL levels materially help data-flow analysis, or when IDA/Ghidra/radare2 ⁩

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-binary-ninja

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

FirmaFirmado, ed25519
xsGV5J/FCB…sXmunsBA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete524d8265…ba04ac99
524d8265dbb6…7c2cba04ac991 archivo · ⁦2.4 KB⁩
EscaneoBajo1 hallazgo
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-binary-ninja@ee0e0c5

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

When it applies

You're analyzing an in-scope binary (scope.txt / client-owned / your own sample — tradecraft-scope-roe) and Binary Ninja is the chosen tool, its intermediate languages genuinely help (SSA-form data-flow questions), or a high-impact conclusion from reverse-eng-ida, reverse-eng-ghidra, or reverse-eng-radare2 deserves a second decompiler's opinion. Binary Ninja is commercial software — it needs a valid Vector 35 license, installed by the user.

Why it works

Binary Ninja lifts every function into layered ILs — LLIL close to the machine, MLIL in SSA form (variables versioned, so data flow is explicit), HLIL close to source. Questions like "where does this attacker-controlled value come from" become IL queries instead of manual register tracking, and the whole analysis is scriptable through one Python BinaryView API.

Method

  1. Baseline the target first — record file hash, architecture, entry points, segments, imports/exports, and representative strings before touching anything. Work on a copy whenever you intend to patch or save database changes.
  2. Pick the integration:
    • GUI / Python API — preferred when Binary Ninja is already open or analysis is interactive.
    • MCP bridge — only when explicitly requested. The reviewed community option is fosdickio/binary_ninja_mcp (GPL-3.0, not an official Vector 35 component; min Binary Ninja build 4000). Keep its HTTP listener on 127.0.0.1:9009 — never expose it to the network. Pin the bridge version:
      text
      npx -y [email protected] --host 127.0.0.1 --port 9009
      The bridge only works once Binary Ninja is running with a binary open and the plugin endpoint responds; register it only in the MCP client the user chose. Discover the live tool list rather than assuming every upstream function exists (families include view selection, list_imports, list_exports, list_strings, decompile_function, get_il, callers/callees, xrefs, types, comments, renames, byte patching).
  3. Navigate by references, not linearly. Follow call sites and cross-references before interpreting any function in isolation.
  4. Pick the right IL level per question: HLIL for readable logic, MLIL SSA for data-flow tracing, LLIL/disassembly when the lifting loses instruction-level behavior (self-modifying code, exotic instructions, anti-analysis tricks).
  5. Annotate incrementally — names, comments, types — keeping original addresses in your notes so every renamed symbol stays traceable.
  6. Treat mutations as mutations. Byte patches, prototype changes, and saved-file writes happen only when requested, on a preserved copy of the original artifact.
  7. Cross-check high-impact conclusions with a second evidence source or another disassembler before they go in a report.

Gotchas

  • The lifting lies occasionally — HLIL can drop or fold behavior; when pseudocode contradicts the disassembly, trust the disassembly and drop to LLIL.
  • License-gated — if Binary Ninja can't open the target or isn't licensed, fall back to reverse-eng-ghidra (free) rather than stalling.
  • The MCP bridge is third-party and GPL-3.0 — review that boundary before installing it; keep it localhost-only.
  • "IL looks too clean" on packed samples — unpack first (reverse-eng-deobfuscation); lifted junk reads like logic if you want it to.
  • Analyze untrusted binaries in an isolated VM.

Verify success

Report concrete addresses, function names, the IL level each conclusion was drawn at, supporting strings/imports, a confidence note, and reproduction steps — so a reviewer can re-walk the analysis in the GUI and land on the same functions.

References

Binary Ninja docs & Python API; fosdickio/binary_ninja_mcp (GPL-3.0 bridge); Vector 35.


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. 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 2026ee0e0c5524d8265Firmada–

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