Binary Ninja reverse engineering
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
- 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.
- Pick the integration:
- Navigate by references, not linearly. Follow call sites and cross-references before
interpreting any function in isolation.
- 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).
- Annotate incrementally — names, comments, types — keeping original addresses in your notes so
every renamed symbol stays traceable.
- Treat mutations as mutations. Byte patches, prototype changes, and saved-file writes happen
only when requested, on a preserved copy of the original artifact.
- 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.
1---2name: reverse-eng-binary-ninja3description: >4 Reverse engineer in Binary Ninja — HLIL/MLIL/LLIL inspection, strings/imports/exports,5 cross-references, types, patching, Python API automation, and the optional MCP/HTTP bridge. Load6 when the user picks Binary Ninja, when its IL levels materially help data-flow analysis, or when7 IDA/Ghidra/radare2 results need an independent cross-check. Signals: "binaryninja", HLIL/MLIL,8 BinaryView scripting, Vector 35, localhost:9009 bridge.9domain: reverse-engineering10type: technique11stability: learning12modes: [pentest, bugbounty]13severity: medium14mitre: [T1592.002]15cwe: [CWE-121, CWE-798]16tools: [binary-ninja, binary-ninja-mcp]17schema_version: 118metadata:19 source: https://skillmd.com/skills/noorqureshi/reverse-eng-binary-ninja20---2122# Binary Ninja reverse engineering2324## When it applies25You're analyzing an in-scope binary (`scope.txt` / client-owned / your own sample —26`tradecraft-scope-roe`) and Binary Ninja is the chosen tool, its intermediate languages genuinely help27(SSA-form data-flow questions), or a high-impact conclusion from `reverse-eng-ida`,28`reverse-eng-ghidra`, or `reverse-eng-radare2` deserves a second decompiler's opinion. Binary Ninja is29commercial software — it needs a valid Vector 35 license, installed by the user.3031## Why it works32Binary Ninja lifts every function into layered ILs — LLIL close to the machine, MLIL in SSA form33(variables versioned, so data flow is explicit), HLIL close to source. Questions like "where does this34attacker-controlled value come from" become IL queries instead of manual register tracking, and the35whole analysis is scriptable through one Python `BinaryView` API.3637## Method381. **Baseline the target first** — record file hash, architecture, entry points, segments,39 imports/exports, and representative strings before touching anything. Work on a copy whenever you40 intend to patch or save database changes.412. **Pick the integration:**42 - **GUI / Python API** — preferred when Binary Ninja is already open or analysis is interactive.43 - **MCP bridge** — only when explicitly requested. The reviewed community option is44 `fosdickio/binary_ninja_mcp` (GPL-3.0, not an official Vector 35 component; min Binary Ninja45 build 4000). Keep its HTTP listener on `127.0.0.1:9009` — never expose it to the network.46 Pin the bridge version:47 ```48 npx -y binary-ninja-mcp@1.0.0 --host 127.0.0.1 --port 900949 ```50 The bridge only works once Binary Ninja is running with a binary open and the plugin endpoint51 responds; register it only in the MCP client the user chose. Discover the live tool list rather52 than assuming every upstream function exists (families include view selection, `list_imports`,53 `list_exports`, `list_strings`, `decompile_function`, `get_il`, callers/callees, xrefs, types,54 comments, renames, byte patching).553. **Navigate by references, not linearly.** Follow call sites and cross-references *before*56 interpreting any function in isolation.574. **Pick the right IL level per question:** HLIL for readable logic, MLIL SSA for data-flow tracing,58 LLIL/disassembly when the lifting loses instruction-level behavior (self-modifying code, exotic59 instructions, anti-analysis tricks).605. **Annotate incrementally** — names, comments, types — keeping original addresses in your notes so61 every renamed symbol stays traceable.626. **Treat mutations as mutations.** Byte patches, prototype changes, and saved-file writes happen63 only when requested, on a preserved copy of the original artifact.647. **Cross-check high-impact conclusions** with a second evidence source or another disassembler65 before they go in a report.6667## Gotchas68- **The lifting lies occasionally** — HLIL can drop or fold behavior; when pseudocode contradicts the69 disassembly, trust the disassembly and drop to LLIL.70- **License-gated** — if Binary Ninja can't open the target or isn't licensed, fall back to71 `reverse-eng-ghidra` (free) rather than stalling.72- **The MCP bridge is third-party and GPL-3.0** — review that boundary before installing it; keep it73 localhost-only.74- **"IL looks too clean" on packed samples** — unpack first (`reverse-eng-deobfuscation`); lifted75 junk reads like logic if you want it to.76- Analyze untrusted binaries in an isolated VM.7778## Verify success79Report concrete addresses, function names, the IL level each conclusion was drawn at, supporting80strings/imports, a confidence note, and reproduction steps — so a reviewer can re-walk the analysis in81the GUI and land on the same functions.8283## References84Binary Ninja docs & Python API; fosdickio/binary_ninja_mcp (GPL-3.0 bridge); Vector 35.8586---87_Portions adapted from [reverse-skill](https://github.com/zhaoxuya520/reverse-skill) by zhaoxuya520, MIT License._