rea

Somewhere on your machine sits a binary you can't ask questions to. The app whose maker vanished. The driver that almost works. The old tool you'd fix yourself if fixing meant anything other than weeks in a disassembler. Everyone in software owns one of these, and for thirty years the only people who could open the box were security researchers, console hackers, and a small priesthood fluent in assembly.

This month, the box started answering. Hacker News put two reverse-engineering projects on its front page in one week. The first ports PlayStation 5 games to PCs with no emulator, just a rebuilt set of the console's system libraries. The second is REA, and its pitch fits in a sentence: your agent can ask a compiled binary questions and get answers back. They took about a hundred thousand stars between them, in a week.

REA is an MCP server. One install, and your coding agent can open binaries, decompile functions, trace how an app behaves, compare two versions. Underneath, the old instruments still do the work, Ghidra and friends. The change is who gets to hold them. REA doesn't make your agent smarter. It hands it glasses. Keep that distinction; the whole trend lives inside it.

The record so far

Six days on the daily board this week, 85,658 stars added, a 1,092 percent week. The repo is six months old and run mostly by one person, who shipped four major versions in six days once the wave started.

The repair shop opens

The first thing people did with cheap reading was fix things. In the launch thread, one commenter handed an agent a stubborn old printer driver, EXE and DLLs, and typed "reverse engineer this printer driver". The session ended with a test page printing. Another recovered the file formats of MS-DOS games and rebuilt the logic. Nobody cracked a vault. They fixed a printer. That's the tell: the boring jobs went first, because boring jobs are where reading was the only barrier.

Security reading showed up too, on both sides of the line. Google's Big Sleep agent reached a SQLite vulnerability before the attackers did; their threat-intelligence lead called it "the first time an AI agent has been used to directly foil efforts to exploit a vulnerability in the wild." Anthropic, in its own disclosure, described a state-linked crew whose agents handled an estimated 80 to 90 percent of the reconnaissance and exploitation. Defense and offense got the same discount.

The old hands in the thread kept two useful dampeners. One: an agent with REA mostly saves you the ceremony of installing Ghidra; the instruments were always there. Two, in a commenter's words: the output "looks good, not so great at generating something that actually is good." Decompiling is the easy half. Knowing the rebuild is faithful is the work.

Your moat has a version number

Closed source was always protected twice: copying it is illegal, and reading it is expensive. The first protection still holds. The second is what just got cheap.

Line up software's defenses by how much they lean on being hard to read. A compiled binary is at the top. Obfuscation sits below it. Then visible-but-vast code. Domain knowledge barely leans on opacity at all, and it's the safest of the four for exactly that reason. Agents attack that ladder from the top, and every model release re-runs the attack, because the glasses stay the same while the eyes behind them keep upgrading.

What survives is whatever never needed the secrecy: your data, your users, your distribution, your reputation. The industry's decade-long move to services now looks like an early retreat from exactly this spot. If your moat is that nobody can see inside, your moat has a version number on it.

The brick suppliers have opinions

There's a third force in this story, and it isn't the attackers or the defenders. It's the labs. Point REA at security work and you'll notice an asymmetry: models rarely refuse to decompile, but they often refuse to hunt for exploits. One commenter expects frontier lockdowns to "make this a lot harder over time." The sharpest line in the thread warned that restrictions "kill the talent pipeline," because the people they stop are students and repairers, not professionals.

So no, this isn't a slope you can chart. It's a negotiation among three parties: the ones taking the wall down, the ones defending it, and the suppliers of the bricks, deciding how the bricks may be used. The direction is clear. The rate is negotiated.

The law assumed scarcity

The rules around reverse engineering were written when the skill was rare, and it shows. Sony sued Connectix over its PlayStation emulator in 1999 and lost on appeal: reading code for compatibility is fair use. Bleem! won every round in court and died anyway, bled dry by legal costs. Yuzu settled with Nintendo for 2.4 million dollars. Thirty years, one lesson: you can win legally and still lose everything.

The PlayStation porting tool from the top of this article stands in that exact tradition, describes itself as interoperability research, and lives one takedown notice from the same fight. Rules written for a priesthood can't govern a congregation. The gray areas widen on their own.

What it means on Monday

For most readers the use case is the repair shop, not the vault. That dead dependency, that binary you own and could never question: it's askable now, or getting there. Calibrate as you go. This month's honest ceiling is partial understanding with receipts; REA itself concedes the point, stamping every answer with what it could not verify. And keep it to software you own or are authorized to inspect. That's the project's stated line too. To see the glasses yourself:

npx rea-agents setup

If you ship closed software, this week is a good moment to sort your moat into two piles: the part that's code nobody can read, and the part that would survive the reading. The first pile has an expiry date now. The second is the one that was ever real.