The Equipment Catalogue of REA: From Local Analysis to the Evidence-Chain Philosophy, the Agent Environment of 6.8.0, and a Memo of Three Breaking Changes

Every hunter deserves an equipment register. The object of today’s pilgrimage is REA — a register that catalogs an entire arsenal of reverse engineering and hands it to AI agents over MCP.

I. What It Is: An Arsenal Plus an Evidence Chain

REA (the npm package rea-agents) is an MCP server plus CLI covering native binaries (through the hands of Hopper/Ghidra/IDA), JS/Electron apps, .NET assemblies, Android APKs (JADX), adb devices, Frida instrumentation, captures (HAR/SAZ), firmware (binwalk), and Go/Rust/WASM/EVM bytecode — local analysis, no uploading of target files. Its most distinctive selling point is the evidence chain: every conclusion ships with its evidence and its limits, leaving the agent no room for confident claims without receipts. Created in April 2026, it has reached 278k stars and 36 releases, iterating at speed.

II. 6.8.0: The Simulated Environment and the Format Expansion

The headline feature of the new edition is Agent Environment: build a local simulated environment from network captures, browser scenes, even a single prompt, and expose only derived reads plus evidence-confirmed writes — letting the agent reproduce and verify behavior without touching the real application. It is the rare case of an ethical boundary made into a product feature. The format catalogue expands in step: GPU code objects (CUDA/HIP), BEAM, Python bytecode, Unity IL2CPP metadata, Godot PCK, PyInstaller, Node.js SEA, GameCube/Wii DOL, devicetree, PE signature certificates and TLS callbacks, ELF notes — from console firmware to GPU microcode, the hunting grounds have almost no border. Large projects no longer lose their way either: function analysis returns token-saving summaries by default, functions can be matched across builds, and pseudocode can be exported as a directory for continued analysis.

III. Three Breaking Changes and One Official Gate

Three items for the memo: analyze_function now defaults to summary mode, full output requires detail: complete; the jsonl output format appends a $rea metadata record at the end; the Node version bar is hard — ^22.23.4 || ^24.22.1 || >=26.12.1, versions 23 and 25 unsupported and the installer will not upgrade for you. And the entry most relevant to this workshop: the 6.8.0 fix list explicitly notes that setup preserves aliased Hermes server tables — REA officially supports registering its MCP into Hermes, one command away with npx rea-agents setup. Its Android capabilities (APK signature declarations, DEX static-final field values, adb device analysis, Frida) are natural kin to the APK battlefields this workshop plows year-round.

IV. The Lesson of the Equipment Register

The history of equipment is the history of cleared hunting grounds: once an agent can hold evidence-chained conclusions and rehearse safely inside simulated environments, reverse engineering stops being a craft and becomes an auditable process. REA made how do you prove it as first-class a question as how do you find it — among all the agent arms races, this is the kind of maturity most worth recording.