Reverse Engineering Engine
Repository: heaven-hm/rea-engine.
Reverse Engineering Engine builds directly on morluto/rea, retaining its MIT license, attribution and working integrations. The package identity is rea-engine; compatible rea and rea-agents command aliases are retained. Registry metadata is configured for io.github.heaven-hm/rea-engine; this does not imply npm or MCP Registry publication.
What differs from upstream REA
| Area | Reverse Engineering Engine addition | Source / reproducible evidence |
|---|---|---|
| Autonomous reconstruction | Persistent checkpoints, bounded build/test/repair, rollback, mismatch regression inputs | Controller, 25/25 fixture report |
| Unknown function investigation | Existing static providers feed runtime hypotheses and independent bounded affine reconstruction | Discovery, recovery |
| Runtime/static correlation | Owned Frida Gadget profile checks binary identity, ASLR and instruction prefix, records arguments/returns and cleanup | Adapter, five-call report |
| Conditional verification | Z3 checks extracted scalar expressions under explicit assumptions | Proof implementation, verification guide |
| Tool installation and bundles | Reuse installed tools; pinned official downloads, hashes, health checks, offline wheel/source bundle builder | Bootstrap and license limits |
| Coding-agent integration | Existing CLI/MCP plus autonomous investigation operations and packaged skill instructions; host Codex/Claude can operate them | Agent workflow, workflow guide |
| Interface | Local evidence/status dashboard with pause/resume/stop | Dashboard |
These are additions to the upstream tool ecosystem. Ghidra, native UI, browser analysis and general Frida capabilities already exist upstream and are not claimed as inventions of this fork.
Software and game: exact measured comparisons
| Target | Result | Proof |
|---|---|---|
| LTRData Luhn utility, reconstructed from its published .NET binary | 5/5 suites: identical terminal bytes, 230 numeric/Unicode lines plus mode, usage and termination cases | Report, complete execution evidence, reconstructed executable |
| Published TicTacToe-AI Windows managed game, rebuilt from recovered code/resources | 19,683/19,683 board configurations: identical observed state bytes; 6/6 frames: identical PNG bytes | Report, complete execution evidence, original executable, rebuilt executable and source |
| Native branch validation fixture | 25/25 declared cases after repair | Report |
| Installed Apple Calculator | 10/10 final numeric-display comparisons in the recorded smaller suite | Report; complete UI and expanded suite remain unverified |
These results prove exact equality of the listed captured bytes, not byte-identical executable files or universal equivalence. Every original/replica executable hash differs. The game comparison exhausts the defined board input space for its win/draw function; AI, RNG, all menus, timing and whole-game behavior remain unverified. The Windows managed artifacts ran on macOS .NET/Mono; this is not proof of native Windows OS execution or native AppKit port fidelity.
The analysis used REA's inspect-managed-members, import-managed-reconstruction and capture-process workflows, with ILSpy recovery and real compilation. The host coding agent operated the engine; no model API key was required. Game source was recovered from the binary, not consulted from the original repository. A pinned original source archive was subsequently retained solely for GPL redistribution obligations. The independent software implementation preserves a recovered quirk: checksum parity counts UTF-16 string length, including punctuation.
Software capture proof viewer
This is an actual screenshot of the engine's proof viewer, captured through REA's owned browser scenario after recomputing the supplied terminal-file hashes. It shows recorded original/replica CLI output; it is not an original-app GUI screenshot. Browser evidence and verified cleanup.
Actual original and rebuilt game renders
These are actual Form.DrawToBitmap renders after the same button-handler sequence on the same Mono/X11 runtime. They are not Windows desktop screenshots. Their PNG SHA-256 is identical: 67673e4f3536084732a35c6da809ea5a69ea89afb0f336c3870a9b0baaa855be.
| Original compiled game | Rebuilt game |
|---|---|
![]() |
![]() |
Interactive proof report · Reproduction and scope · artifact SHA-256 inventory
Installed tools versus distributed tools
Development health checks confirmed Frida 17.23.3, LIEF 1.0.0, Z3 5.1.0.0, Capstone 5.0.9 and Pillow 12.3.0. Ghidra/radare2 and native compilers are reused locally. Bundled now: the signature-verified ILSpy package and the built X11 libgdiplus library with source and licenses. The preview release also carries the checksum-verified, unmodified Ghidra 12.1.2 archive; see its manifest. A clone does not contain every installed external tool binary. The installer and offline bundle builder are shipped in source; generated local bundles are not a license-approved public distribution. Frida/LIEF native dependency source and license coverage require further audit. Optional licensed tools and Apple Calculator are not redistributed. See tool profiles and limitations.
Build and use this repository
git clone https://github.com/heaven-hm/rea-engine.git
cd rea-engine
npm ci
npm run build:cached
node scripts/print-mcp-config.mjs /absolute/path/to/target --local
node scripts/rea.mjs --help
Use the printed local MCP configuration with your host coding agent and the built packaged skill. A published upstream npm package is not this fork. The implementation retains compatible command names while the product identity is Reverse Engineering Engine.
Documentation
- Autonomous reconstruction and host-agent workflow
- Executed benchmarks and reproduction
- Static/runtime tool bootstrap and offline bundles
- CLI and evidence
- Ghidra provider
- Managed .NET analysis
- MCP contracts
- Licensing and third-party notices
Report issues and contribute at heaven-hm/rea-engine.
Latest validation: the complete managed benchmark command passed again with verified owned-display cleanup. The focused autonomy regression batch passed 37 tests with 2 skipped; type and lint checks passed. Execution logs and checksum inventory. These are scoped development checks, not certification of all REA capabilities.


