Reverse engineer anything with agents, from app behavior down to native binaries.
layout: home
hero: name: REA text: Reverse Engineer Anything tagline: Understand binaries, applications, and runtime behavior with one CLI and MCP server. actions: - theme: brand text: Get started link: /installation - theme: alt text: View on GitHub link: https://github.com/morluto/rea
features:
- title: Investigate with your agent details: Connect REA to your coding agent, describe the app or feature you want to understand, and follow the evidence. link: /mcp-prompts
- title: Inspect across formats details: Explore native binaries, JavaScript and Electron apps, .NET assemblies, Android packages, firmware, and websites. link: /installation
- title: Keep the evidence details: Analysis runs locally and returns observations, limitations, and unknowns through the CLI and MCP. link: /mcp-contracts
Start with one command
npx rea-agents setup
Choose your agent, review the planned changes, and approve setup. Native binary analysis can use an existing Hopper, Ghidra, or IDA installation; static JavaScript analysis needs no native analysis engine.
For a first result from an extracted JavaScript application or ASAR:
npx -y rea-agents@latest analyze-javascript-application /absolute/path/to/app --json
See installation and setup for requirements and configuration.
For runtime instrumentation, see the Frida guide.
Choose a guide
For development, use testing, client verification, tool design, admission limits and recovery, and releasing. Reconstruction readiness describes a development conformance verifier. The 6.2 migration records that release's compatibility changes; the roadmap tracks future work.
