REA (Reverse Engineer Anything) at a glance
Checked 15 Oct 2026REA (rea-agents 6.5.0, Oct 2026) connects agents such as Claude Code, Codex or Cursor to local analysis tools over MCP. Native-binary work drives an existing Ghidra, IDA or Hopper install; JS/Electron and .NET inspection work without one. MIT. Needs Node.js 22.19+. Its README pitches rebuilding features seen in other apps; its disclaimer limits use to lawful, authorised analysis, and you must respect target licences and terms.
RepoQuarry. “REA (Reverse Engineer Anything).” Checked 15 Oct 2026. https://repoquarry.dev/projects/reaHow much of IDA Pro does it replace?
1 of 4 jobs. Agent layer over Ghidra, IDA or Hopper; it does not disassemble or decompile native code on its own.
For disassembly, decompilation, debugging, see other IDA Pro alternatives. You may also need to build an interface, an API server and hosting yourself.
Facts, with sources
Every answer links to where we found it. We read the documentation; we did not install it.
REA analyzes targets locally. Your agent receives the tool results, and its model provider has its own data policy.github.com · rea#faq ↗ 1d ago
REA-authored code is licensed under MIT. Third-party material retains its own licenses and copyright noticesgithub.com · LICENSE ↗ 1d ago
REA is built for lawful analysis: security research, malware and incident analysis, vulnerability research and coordinated disclosure, CTFs and education, interoperability, software preservationgithub.com · DISCLAIMER.md ↗ 1d ago
Deep native analysis uses one of them. Static JavaScript and .NET inspection work without a native analysis engine.github.com · rea#faq ↗ 1d ago
Ghidra and IDA have their own provider-specific host requirements; Windows Ghidra uses the experimental P0 boundary.github.com · installation.md ↗ 1d ago
Choose your agents, review the proposed changes, and approve them. Setup adds REA's MCP server and matching workflow instructionsgithub.com · rea#quick-start ↗ 1d ago