What Take-Two demanded from Microsoft and Discord
Take-Two Interactive, the parent company of Rockstar Games, filed DMCA subpoenas against Microsoft and Discord in the U.S. District Court, Southern District of New York, on August 20, 2026, and the court approved both requests the following day, August 21, 2026. The filings target the source of leaked Grand Theft Auto VI gameplay footage showing driving, basketball, flight, and brawling sequences, and they give Take-Two a court order compelling both companies to identify who is behind the leak before any lawsuit is even filed.
The subpoena to Microsoft demands the MachineGuid and MSA device identifiers tied to the suspected leaker's account, the IP addresses used to access it, any phone numbers on file, linked Xbox or Google account information, and the contents of the associated OneDrive storage. The subpoena to Discord goes further still: it demands the identity of every member of three named servers, "Odyssey.gg", "! Odyssey", and "DarkViperAU", that have been active since June 1, 2026, not merely the identity of the person suspected of leaking the footage.
The turnaround between filing and court approval, laid out below, shows how quickly a request like this can move once a rights holder decides to pursue it.
| Filed | Court approved | Response deadline |
|---|---|---|
| August 20, 2026 | August 21, 2026 | September 4, 2026 |
Why Take-Two went after whole servers, not one user
The leaks at the center of this case surfaced through a persona calling themselves CyberLeek, who posted driving, basketball, flight, and brawling gameplay footage that traces back to unreleased builds of Grand Theft Auto VI. CyberLeek's posts were reportedly tied to a manifesto opposing pre-orders and paywalled downloadable content, along with a linked promotion for a meme coin, giving Take-Two's investigators both a stated motive and a financial angle to follow alongside the leaked footage itself.
Take-Two's subpoena does not stop at CyberLeek's own account; it asks Discord to identify every member of "Odyssey.gg", "! Odyssey", and "DarkViperAU" going back to June 1, 2026, regardless of whether an individual member ever touched the leaked files. That scope only makes sense if Take-Two's theory is that the leak moved through, or was coordinated inside, those communities, and it treats every member's presence in the server, not their conduct, as reason enough to be identified.
The precedent this sets for anyone running a community
A DMCA subpoena and a civil lawsuit are two different tools, and the difference matters more than the outcome of this one leak. A DMCA subpoena lets a copyright holder go directly to a court clerk with a request tied to a takedown notice, without first filing a lawsuit or notifying the people whose data it seeks, and courts typically approve them as a procedural matter rather than after the kind of adversarial fact-finding a lawsuit would involve; Take-Two's one-day turnaround between filing and approval is a clean illustration of how fast that process can move.
Any owner-operator running a Discord community, a GitHub organization, a Slack workspace, or any other platform that hosts user-generated content should read this filing as the new practical floor for how easily a rights holder can compel a platform vendor to identify an entire userbase. Take-Two did not need to prove who leaked the footage, sue anyone, or even name every member it wanted identified; it needed a copyright claim, a subpoena request, and two platforms willing to comply once a court signed off.
What happens next, and the standard it leaves behind
Microsoft and Discord have until September 4, 2026, to respond to the approved subpoenas, and neither company has publicly detailed how it plans to comply or contest the requests. Whatever data eventually changes hands, the identities of everyone who has belonged to "Odyssey.gg", "! Odyssey", or "DarkViperAU" since June 1, 2026, are now in scope, a fact that will outlast whatever happens to CyberLeek personally.
The lasting story is not whether Take-Two catches its leaker; it is that unmasking an entire community's membership turned out to require nothing more than a DMCA subpoena, a receptive court in the Southern District of New York, and two platform vendors with the records on file. Every operator running a community on someone else's platform now has a concrete answer for how far that platform can be compelled to go, and it did not take a trial to find out.
Read next: Xbox Layoffs: Two Labor Laws, One Company | GitHub's Outage Bill: A Doubled Commit Load
