Sunday 4 October 2026
Afternoon EditionRSS
ZOTPAPER

News without the noise

ZOTPAPER
Tech

Massive GTA V Data Leak Reveals Early GTA VI Map, Canceled DLCs, and Alternate Ending

Archived files from 2022 leak show early Leonidas map playable in GTA V, scrapped 'Agent Trevor' expansion, and liquid nitrogen death for Trevor

By LineZotpaper
Published
Read Time2 min
A 192GB trove of GTA V data from a 2022 leak has been newly analyzed, revealing early conceptual builds of the GTA VI map, outlines of a canceled Liberty City expansion, a scrapped single-player DLC called 'Agent Trevor', and an alternate ending where protagonist Trevor Philips dies by crashing into a liquid nitrogen tank.

The recently surfaced 192GB archive, part of a leak that occurred in 2022 alongside confirmation of GTA VI development, has been dissected by fans and enthusiasts. X user TJGM shared screenshots of an early build of the GTA VI map, labeled 'Leonidas', which appears to be based on satellite imagery and Google Maps Street View. The build is dated 2014 to 2015 and is playable within GTA V, indicating Rockstar was working on a sequel even before the original game's 2015 PC release.

Further digging uncovered a map outline for Liberty City, accessible via the CodeWalker map editor, which was likely intended for an unreleased DLC. The outline is significantly larger than the Liberty City in GTA IV. Additionally, details of a scrapped single-player expansion called 'Agent Trevor' were found, including interiors for a massive bunker, a spaceship, and an Arab mansion — reportedly three times larger than similar assets in the final game.

Voice-over recordings for cut content were also leaked. One clip features Brucie Kibbutz from GTA IV speaking with Franklin in a mission. Another reveals an alternate ending for Option A of GTA V's finale, where Trevor crashes into a liquid nitrogen tank, freezes, and shatters — a stark contrast to the final version. These files represent a rough draft, distinct from a more recent full working build of GTA VI that was leaked separately.

§

Analysis

Why This Matters

  • The leak offers an unprecedented look at Rockstar's early development process for GTA VI, showing how concepts evolved years before announcement.
  • Canceled DLCs and alternate endings reveal story directions that fans have long speculated about, providing closure and fueling discussion.
  • The continued circulation of leaked data underscores persistent security vulnerabilities at Rockstar, raising questions about protection of in-development projects.

Background

Rockstar Games confirmed GTA VI was in development in February 2022. That same year, a notorious hacker leaked a massive cache of data, including early footage and code. More recently, a full working build of GTA VI was leaked, drawing significant attention. The company has a history of scrapping DLC for GTA V; the Liberty City expansion and 'Agent Trevor' were never confirmed publicly. The 192GB archive appears to be from the initial 2022 breach, but has only now been fully analyzed by the community.

Key Perspectives

Fans and Enthusiasts: Excitement over seeing early map concepts and cut content, fueling lore discussions and hope that some ideas might be reused in future Rockstar titles. Rockstar Games: Likely frustrated by the ongoing exposure of internal assets; the company has not commented on this specific analysis. The leaks may have influenced development decisions or security protocols. Skeptics: Caution that these are very early, rough concepts — not representative of the final GTA VI product. The Liberty City outline is just a shell, and the DLC assets are recycled and incomplete.

What to Watch

  • Whether Rockstar issues a statement or takes legal action to remove the newly surfaced content.
  • Further data mining of the 192GB archive, which may reveal more unreleased missions, dialogue, or map details.
  • Impact on GTA VI's marketing timeline; the company may accelerate official reveals to counter leaks.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.

How we workReport an errorSubscribe