A GTAForums user uploads 90 gameplay videos of Rockstar's upcoming GTA VI, claiming they were behind last week's Uber hack and may leak GTA V and VI source code
Context & Ripple Effects
The claimed footage was followed by Rockstar’s confirmation of an unauthorized network intrusion, while the company said GTA VI development would continue as planned. The episode therefore moved from an unverified forum post to a disclosed security incident affecting Rockstar’s control over pre-release material.
Later coverage records GTA V source code appearing online after the breach, while Rockstar subsequently resumed its planned GTA VI reveal cycle with a first official trailer. That sequence makes the source-code threat more consequential than the footage alone.
First-order effects
- Rockstar must contain the intrusion and manage the public circulation of unfinished GTA VI material while maintaining development plans.
- The claimed threat to release GTA V and GTA VI source code raises the immediate stakes from exposure of promotional assets to potential exposure of software assets.
Second-order effects
- Rockstar’s official marketing loses exclusivity over the first impressions of GTA VI, increasing the importance of controlled trailers and communications in setting expectations.
- A later apparent GTA V source-code leak shows how a breach can persist beyond the initial footage, extending remediation and distribution-control work after the first disclosure.
Third-order effects
- For major game publishers, pre-release security is becoming part of release management: intrusion response must protect both unfinished creative work and the code that underpins existing titles.
- If source-code leakage follows high-profile intrusions more often, publishers will face a longer-lived security burden than removing leaked videos, because copied code can be redistributed outside their platforms.
The trend: Game publishers are treating cyber intrusion response and control of pre-release material as a continuous release-management problem rather than a one-time leak takedown task.