Reverse engineering with REA, one real workflow at a time.

Install REA with npx rea-agents setup, connect Claude Code, Cursor or Codex over MCP, check providers and capabilities, and run your first analysis.

Use REA with free Ghidra to analyze a native binary you compiled: analyze, search strings, decompile, follow xrefs and trace a feature from CLI or AI agent.

Analyze an Electron app with REA: read app.asar, map modules and imports, use source maps, follow preload and IPC channels, and hand native add-ons to Ghidra.

Analyze an open-source Android APK with REA: decompile classes with JADX, decode resources with Apktool, pull packages over ADB, identify Flutter Dart builds.

Build a small crackme, then solve it with REA and a coding agent: find the check, extract the table, write a solver and prove the flag with Evidence IDs.

Use REA to capture a page, take screenshots, observe network requests, read HAR and Fiddler SAZ files, and find the front-end code that makes each API call.

Inspect .NET assemblies with REA without running them: identify the PE/CLI artifact, read metadata and CIL, compare members across builds, and handle NativeAOT.

Use REA Evidence to compare two versions of an open-source app: save snapshots, validate and export bundles, run compare, and import historical source.

Unpack an OpenWrt image with REA's Binwalk and Unblob integration, then hand an extracted ELF to Ghidra. Covers Linux x64 limits, budgets and handoffs.

A sourced comparison of REA with GhidraMCP, ida-pro-mcp, r2mcp and Binary Ninja MCP: coverage, backends, install, licensing and best-fit use, as of 2026-10.