Skip to content

meltedinhex/analyst-ai-pack / skills/reverse-engineering-binaries-with-binary-ninja

reverse-engineering-binaries-with-binary-ninja

Verified

Reverse engineers binaries with Binary Ninja using its analysis stack and Python API to enumerate functions, navigate IL levels (LLIL/MLIL/HLIL), and automate annotation and extraction. Activates for requests to reverse a binary with Binary Ninja, script the Binary Ninja API, or work with its intermediate languages.

FileKindSize
LICENSEother340 B
SKILL.mdskill md2.9 KB
references/api-reference.mdmarkdown1.2 KB
scripts/analyst.pyscript2.6 KB

references/api-reference.md

View on GitHub
# API Reference: Reverse Engineering Binaries With Binary Ninja

## Overview

`scripts/analyst.py` generates Binary Ninja Python API analysis scripts that open a view, iterate
functions, and export functions/strings to JSON. `check` reports whether the `binaryninja` API is
importable. It only generates text and does not run Binary Ninja or a sample.

## Dependencies

| Package | Version | Purpose |
|---------|---------|---------|
| binaryninja | licensed | the analysis API (optional for generation) |
| (stdlib) | — | JSON, file IO |

## Core functions

### `check()`
Reports `binaryninja` API availability.

### `skeleton(out, emit)`
Writes a script using `binaryninja.open_view`, `bv.functions`, and `bv.get_strings`.

## IL levels

- LLIL: close to assembly.
- MLIL: variables/SSA reasoning.
- HLIL: readable pseudo-code.

## Usage

```bash
python scripts/analyst.py check
python scripts/analyst.py skeleton --emit functions,strings --out bn_extract.py
```

## Sources

- Binary Ninja Python API — https://api.binary.ninja/
- Binary Ninja IL (LLIL/MLIL/HLIL) — https://docs.binary.ninja/dev/bnil-llil.html
- `open_view`/`bv.functions`/`get_strings` usage from official API documentation
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 321kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 321kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 321kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 321kUpdated Claude CodeCodexVerifiedInstall