Best REA source recovery cases

Rebuilds the 1990s Breakout game's logic in C and checks it against the original x86 program with differential tests and byte-exact compiled output.

The author claims to have tested REA (Reverse Engineer Anything), which went viral on GitHub, using Excalidraw as the test subject, and believes that REA's value lies in integrating complex analysis workflows rather than cracking everything. The post does not include project links, steps, or demonstration evidence.

วิดีโอภาษาไทยที่พาไปเจาะเบื้องหลังโปรเจกต์ Reverse Engineer Anything (REA) บน GitHub ผ่านการอ่าน Source Code และกรณีศึกษาสาธารณะ ตั้งแต่การวิเคราะห์แอป Android, Notion, เกมเก่า DX-Ball ไปจนถึงโปรเจกต์ต่อยอดอย่าง Ledger Reborn และ ReaCut พร้อมพูดถึงข้อจำกัดของ REA

Reconstructs a PC-98 DOS shooter's code, matching its 16-bit routines to readable C++ and the historical compiler's output.

A developer compiled their own iOS app into an executable and gave it to AI. Without providing the source code, using REA with Ghidra, the profit/loss calculation formula was restored within 16 minutes. They shared the process from two failures to success after adjusting settings.

A 58-LINE PROMPT TURNS OPUS 5.5 + REA INTO A CLEAN-ROOM LAB FOR ANY APP ON YOUR LAPTOP most builders still use Opus like a chat window. this prompt makes it drive REA down to the binary and come back with evidence the flow from @N01ennn's prompt: MAP > reads the whole app first, then picks one seed: a module, a string or a symbol PATH > follows the real route from your click to the result, down to one function EVIDENCE > every line gets a label. OBSERVATION cites the file, function and line, INFERENCE says what it follows from, UNKNOWN stays on the list and never shrinks SPEC > writes SPEC.md from behaviour only, with inputs, outputs, state, edge cases and errors BUILD > implements your version from the spec alone. when the spec runs out it goes back to investigate instead of filling gaps from memory VERIFY > runs the tests until they pass, then plants one wrong answer. if the tests still pass, they were blind REA picks the engine by target. Node for JS, Electron and .NET, Ghidra, Hopper or IDA for native binaries, JADX for Android APKs, a Chrome browser for websites the scope line sits in the prompt itself. lawful research, interop, preservation or software you own. outside t

▶ ♫

An essay on rebuilding three Touhou games with agents: what verification looks like, where agents help, and how knowledge carries from one project to the next.

A YouTube Short claim-checking REA (morluto/rea) by asking five questions about the open-source Aegis authenticator app before opening its source; it reports 5/5 correct answers and links the repository, but shows no reproducible steps or detailed evidence.

El autor prueba REA (Reverse Engineer Anything), el MCP de ingeniería inversa, usando su propia aplicación de código abierto Elite Pen como caso de estudio, restringiendo el acceso al código fuente para analizar el binario compilado y obtener pseudocódigo.

Software monetisation is dead. AI Reverse Engineer Anything. REA : It maps JavaScript/Electron apps, analyzes apps native binaries, and returns real evidence behind its conclusions so you can rebuild features from scratch. This test demo it on a popular npm package it reconstructed the core logic in minutes and nearly passed every test after one tiny fix.

▶ ♫

An X post describing how AI agents used REA (the reverse engineering MCP) to recover functions from the DX-Ball executable, reconstructing a C version one function at a time with byte-for-byte comparison against the original x86 code.

▶ ♫