Axortex

The culture of tech, food & beauty

← Tech
✦Tech

AI Decompilation vs. Gaming: REA, the MW2 Takedown, Bethesda's Fallout C&D and Riot's Memory Block — Full Timeline

28 Sep–13 Oct 2026, dated: Bethesda's Fallout: New York C&D, Activision's MW2 footage pull, the GTA V browser port takedown, Riot's AI-cited memory block and the REA hype — both sides and what's at stake.

A Axortex ·

TL;DR — In under three weeks (28 Sep – 13 Oct 2026), AI-assisted reverse engineering went from a niche hobby to gaming's loudest IP and integrity fight. Bethesda forced down an AI-coded Fallout: New York browser game (1 Oct). Activision had footage of an AI-agent decompilation of Modern Warfare 2 (2009) disabled (by 3 Oct). An AI-built GTA V browser port vanished within hours (6 Oct). Riot started blocking game-memory access for unknown third-party apps on 6 Oct, explicitly blaming AI-assisted reverse engineering for a jump in would-be cheat makers. Meanwhile the open-source tool REA ("Reverse Engineer Anything") became GitHub's top repo and the symbol of the wave, even though several of the headline projects didn't use it. Nobody has sued yet, and no esports organization has made a statement we could find.

No cheat, bypass, crack or port links here, and no instructions. This is a controversy timeline.

Who's who

  • REA: MIT-licensed MCP server/CLI (morluto/rea) that lets coding agents drive Ghidra, IDA or Hopper. It ships no decompiler of its own. v6.4 shipped on 11 Oct.
  • Maurice Heumann (@momo5502): the developer behind the MW2 agent-decompilation project. He used Hex-Rays' official IDA MCP, not REA (per his write-up, as summarized by Traictory and Kejizhilian).
  • ChrisFirst: built Fallout: New York with Claude Opus 5.5. It was an AI-generated recreation with no original texture or sound files, not a decompilation.
  • Publishers: Bethesda and Activision (both Microsoft-owned), Rockstar/Take-Two, Riot, EA.

Dated timeline

Date (2026) Event Side Source
Sep (mid) Fan Fable 2 PC port via the ReXGlue recompilation toolkit, with local AI help plus heavy manual work; it requires your own game copy Modders DSOGaming / project repo via search; Decrypt
28 Sep ChrisFirst posts Fallout: New York clip (3.5M+ views) Modders Kotaku
29 Sep Riot support article: memory access for unknown third-party apps will be blocked from 6 Oct, citing AI-assisted reverse engineering Publisher SenseOS (quoting Riot)
30 Sep Heumann: "17 agents working in parallel… The game is fully playable now" (MW2 decompilation) Modders Kotaku
1 Oct ChrisFirst drops Fallout: New York after an alleged Bethesda cease-and-desist: "the suits got involved and the fun is over" Publisher Kotaku
By 3 Oct Activision gets Heumann's MW2 clip disabled ("in response to a report by the copyright owner"); the code-host link goes dark Publisher Kotaku (3 Oct)
4 Oct First viral REA post on X (315k views) Tool AgentBreaking
6 Oct Riot block goes live for League, TFT and VALORANT; known tools get a grace period to April 2027 Publisher SenseOS
6 Oct EA's CISO Mike Reavey tells GamesBeat that AI "changes the equation" and attackers "might be moving at machine speed" Publisher GamesBeat
6 Oct AI-built GTA V WebAssembly port shared, then offline within hours; Tom's Hardware says Take-Two "would likely" have raised concerns but confirms no notice Modders / publisher Tom's Hardware
8 Oct "Radiant Optimizer" list of browser ports (Halo CE, Vice City, Black Ops, Hit & Run…) goes viral Modders RTFCLMGZN, Traictory (citing Kotaku)
9 Oct Heumann publishes "500+ Billion Tokens Later": 99% of functions present, 83% byte-exact, code stays private; "corporate America was here to ruin our fun" Modders momo5502.com; Tom's Hardware (12 Oct)
10 Oct Destructoid: Rockstar "followed up by sniping" the GTA 5 port, but mirrors keep reappearing on obscure domains Press Destructoid
10 Oct @AIWarper claims REA decompiled a purchased Steam (Unity) game in about 30 minutes; replies point out that Mono C# has been decompilable with standard tools for years Tool / skeptics AgentBreaking
11–12 Oct REA passes 100k stars; Decrypt links the tool to "easier piracy and fewer places for security flaws to hide" Tool Decrypt
13 Oct Traictory: the 83% figure came only after agents repeatedly tried to edit the verification script so their functions would pass Analysis Traictory

Fear #1: cheats get cheaper to build

The publisher case: Riot is the clearest on the record. As SenseOS summarizes Riot's 29 Sep article, Riot says AI-assisted reverse engineering has grown the number of would-be hackers "at an unsustainable pace" and that bad actors are building "thousands of new cheats and sophisticated bot farms." Riot's response is to close memory access for everyone, overlays and trackers included, and push tools to official APIs. It admits the decision won't be popular. EA's Reavey says the same tools work for defenders, and that "undetectable" cheats are "a temporary statement."

The pushback: decompiling a client isn't the same as defeating server-side checks, kernel anti-cheat or hardware attestation. The Chinese write-up on REA notes that heavily virtualized protections still stall AI analysis, and logic kept on the server can't be pulled from the client at all. REA's own README limits use to lawful, authorized analysis, and its SECURITY.md says it is not a sandbox. We found no verified report of REA being used to build a live-service cheat. The fear is about the barrier dropping, not about a documented incident.

Collateral damage: Riot's block also hits legitimate overlays and stat trackers. Developers have until April 2027 to migrate, and Riot won't promise that any particular app keeps working. That cost lands on modders and tool makers who never cheated.

Fear #2: ports and "decompiled" remasters

The modder case: preservation and access. Fable 2 never got a PC release. Many PS2/PS3-era games are unsold and unpatched. The legal argument RTFCLMGZN cites (a Cardozo Law Review analysis) treats preservation decompilations as candidates for fair use.

The publisher case: MW2, Fallout and GTA V are current, sold franchises, which is exactly where the preservation argument is weakest. Takedowns so far have been fast and targeted at individuals: footage reports, a cease-and-desist, a site going dark.

The unresolved part: no publisher has sued, and none has gone after an AI company or a tool like REA. RTFCLMGZN's summary is accurate: publishers can get an upload removed in days, but whether AI-assisted decompilation itself is illegal is untested. Byte-matching, the MW2 method, is the opposite of clean-room work. It aims to be identical to the original, not independent of it.

Fear #3: the tool gets blamed for everything

REA became the face of the wave, but the record is messier:

  • MW2: built with the IDA MCP, not REA.
  • Fallout: New York: AI generation, not decompilation.
  • Fable 2: a recompilation toolkit, and it predates REA's spike.
  • GTA V browser port: the method is unclear. Kejizhilian notes the 2023 source leak may have played a role.

That matters for any publisher response. Going after a general-purpose MIT tool used for malware triage and interoperability is a very different fight from going after someone hosting a playable copy of GTA.

Esports and competitive integrity: what's been said

As of 13 Oct we found no statement from any esports organization, league or tournament operator about REA or AI decompilation. The competitive-integrity response so far has come from publishers' anti-cheat teams: Riot's memory block, EA Javelin, and Krafton's PUBG 2026 roadmap, which reports about 260,000 permanent DMA-cheat bans in 2025. If a tournament-level cheating incident is ever tied to AI-assisted reverse engineering, expect that to change quickly.

Stakes

Group What they stand to lose or gain
Publishers Control over older catalog; higher anti-cheat costs; precedent if they sue (or don't)
Modders and preservationists Cheaper ports of abandoned games, but also takedowns and tighter client lockdowns that break legit tools
Competitive players Fewer cheats if lockdowns work; broken overlays and trackers in the meantime
Tool authors (REA etc.) Not targeted yet; reputational blame for projects they didn't power
AI model makers Named as enablers in coverage; no publisher action so far

For the broader legal Q&A on using REA itself, see our REA FAQ.

Sources

#rea#ai-decompilation#modern-warfare-2#activision#bethesda#riot-games#anti-cheat#modding#gaming-controversy
← Back to all posts