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-ninjaReverse engineering e 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 installazioni+3 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-ninja

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

FirmaFirmato, ed25519
xsGV5J/FCB…sXmunsBA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto524d8265…ba04ac99
524d8265dbb6…7c2cba04ac991 file · ⁦2.4 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/reverse-engineering/reverse-eng-binary-ninja@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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.

File di questa versione

Permessi

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

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. 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
v2026.10.14-ee0e0c513 nov 2026ee0e0c5524d8265Firmata–

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