About rea-reverse
rea-reverse publishes browser tools that analyze files locally on your device, alongside reproducible guides for inspecting build artifacts, debugging releases and reverse engineering. You can identify an unknown file, check an Android release, inspect a native binary or decode a JavaScript stack trace without uploading the input to this site.
REA, the open-source reverse-engineering tool developed by morluto, is an important guide series here. Its MCP server and CLI connect terminals and AI coding agents to Ghidra, JADX, Apktool, browser capture, firmware extractors and other analysis providers.
This site is not run by the REA project. For the source code, releases and issue tracker, go to the REA repository on GitHub. The package is published on npm as rea-agents, and the project’s own documentation and case studies live at rea.tools.
What you will find here
Practical guides cover file signatures and format checks; Android signing, installation and release checks; source maps, JavaScript bundles and Electron archives; and installing REA and connecting it to Claude Code, Cursor or Codex. The REA series includes analyzing native binaries with Ghidra; inspecting Electron apps, Android APKs and .NET assemblies; tracing website API calls; unpacking firmware; solving CTF challenges; and comparing REA with other reverse-engineering MCP servers.
Editorial process
The guides and tools are published under the rea-reverse organization name. Article bylines identify that publishing identity; individual test environments, sources and limits are documented in the guides.
How guides are written and verified
- REA workflow guides name the release they cover; general file and build guides name the tools and versions relevant to their tests. For REA commands, flags, tool names and platform limits, the reference is the published release of rea-agents on npm and its documentation. Where the repository’s
mainbranch already does more than the release, the guide says so. - Guides record their test environment and real runs on samples built for the purpose (small programs compiled from source, a contract compiled with solc), open-source targets, CTF challenges or targets from the REA showcase. They distinguish captured output from documentation examples and illustrative snippets, and identify platforms or steps that were not run. A static result or a synthetic sample is not evidence of a successful production deployment or a policy approval.
- A REA release number changes after the relevant workflow has been checked against that release. Technical corrections and new checks are recorded by the guide’s update date; presentation or SEO edits alone do not imply that an experiment was rerun.
Corrections
For REA command behavior, consult the official documentation for the release you are using. For other tools and formats, guides link their primary references. If you spot a mistake, tell us through the contact page and include the URL of the guide. Confirmed errors are fixed and the guide’s “updated” date is changed.
Independence
This site is not affiliated with, sponsored by or endorsed by the REA project or morluto. Nothing here is REA’s own documentation, and the guides never present themselves as such. Example targets are open-source programs, programs you compile yourself, CTF challenges, or targets from the REA showcase. See the disclaimer for what that means for your own work.
How the tools are tested
The browser tools have unit tests for their parsers and end-to-end tests that load each tool in real browsers. Their results are cross-checked against the standard tools for each format, for example aapt2 for APKs, zipalign and llvm-readelf for 16 KB page alignment, wabt for WebAssembly and solc’s own selector hashes for EVM bytecode.
Advertising
The site is free to read. It is set up to be supported by Google AdSense ads on guide pages; tools and info pages never carry ads. Ads never change what a guide recommends. The privacy policy explains which cookies ads use and how to opt out of personalized ads.