Discord Not Yet Served in Take-Two’s GTA 6 Leak Case

Discord says it has not yet received a subpoena from Take-Two Interactive in the publisher’s attempt to identify people connected to the latest alleged Grand Theft Auto VI leaks. The clarification matters because it separates two stages that have often been blurred together in coverage and online discussion: a copyright owner can ask a federal court clerk to issue a Digital Millennium Copyright Act subpoena, but the platform must still be served before it receives the legal demand and decides how to respond. On August 25, 2026, Discord marketing director Ryan Rigney said the company had not yet been served by Take-Two and that, once it is, Discord will assess the request’s validity and scope.

That does not mean Take-Two’s legal effort is imaginary or withdrawn. Public reporting and court records show that Take-Two has pursued DMCA subpoena proceedings in the U.S. District Court for the Southern District of New York in connection with material it says infringes its GTA VI copyrights. The visible docket for the Microsoft matter is titled In re Take-Two Interactive Software, Inc., case number 1:2026mc00421. It was filed on August 21, 2026, and lists internet infringement as its cause of action. The court order signed by Judge Jennifer L. Rochon directs the clerk to issue the subpoena for Microsoft Corporation sought by Take-Two.

The distinction is important for players, Discord users and anyone named in online speculation. A court-approved request is not the same thing as an adjudication that a leaker has been identified, that a platform has handed over records, or that an individual has committed a crime. The court record available publicly concerns the issuance of a subpoena for Microsoft; Discord’s statement says it had not been served as of August 25. No public finding in the cited materials establishes the identity of the person or people behind the account or persona labelled “CyberLeek.”

What Discord actually said on August 25

Rigney’s statement was concise but unusually consequential in a story driven by fast-moving reports and reposted screenshots. He wrote:

“Discord has not yet been served with a subpoena from Take Two. When we do, we’ll evaluate the validity and scope before responding.”

The wording does not deny that Take-Two sought the subpoena. It also does not say Discord will refuse to comply. Instead, it establishes the platform’s status at that moment: no service had occurred, and Discord had not yet reached its response stage.

That status is narrower than some headlines might suggest. “Not yet served” does not invalidate the reported filing, erase the request or determine what Discord will do later. It means the legal document had not been formally delivered to Discord at the time of the statement. Conversely, it does not prove that all of the information described in reporting will ultimately be disclosed. Rigney explicitly reserved Discord’s evaluation of both validity and scope, two questions that become central when a request seeks data associated with more than a single account.

For readers trying to follow the story responsibly, the most accurate present-tense description is therefore limited: Take-Two has sought identifying information through DMCA subpoena proceedings; the Microsoft subpoena was ordered issued on August 21; and Discord said on August 25 that it had not yet been served. Anything beyond that, including claims that Discord has already delivered user data or that a particular user has been unmasked, is not established by the materials verified here.

What Take-Two is seeking from Microsoft and Discord

Reporting based on the filings describes requests far broader than a simple username lookup. Take-Two filed two DMCA subpoena requests in the Southern District of New York on August 20, 2026, seeking to identify the person or people associated with the “CyberLeek” persona. The reported requests set September 4 as the date by which Microsoft and Discord were asked to produce records.

For Microsoft, the reported request includes MachineGuid and Microsoft account device identifiers, registration and last-login IP addresses, phone numbers, linked connections such as Google and Xbox accounts, and OneDrive content associated with accounts that communicated in three named Discord servers since June 1, 2026. It also seeks Microsoft business and investigative records associated with an internal investigation of the “cyberleek” persona sufficient to identify the user or users involved, according to reporting that quotes the filing.

For Discord, reporting describes a demand for identifying information linked to accounts that were members communicating in specified servers during the same June 1-to-present period. The reported scope names the handles CYBERLEEK, CINEMATICROCKSTAR and Surfer24k, as well as replacement handles cyberleek_west and surwest. It also names three communities: Ødyssey.gg, “! Odyssey,” and a server described in the filing as the DarkViperAU editors’ server.

The word named needs care. Being mentioned in a subpoena request is not itself an accusation, conviction or factual conclusion about the operators, moderators or members of any listed server. The reported language seeks records that may help identify an alleged infringer. It does not publicly establish that every account holder in a community created, obtained, uploaded or knowingly redistributed protected GTA VI material. This distinction is especially important because a request framed around membership or communication can encompass people whose connection to the alleged infringement is uncertain from the public record.

Why the reported scope has drawn attention

The scale of the described data request is the key issue in this development, not simply the fact that Take-Two is protecting a forthcoming game. Copyright owners routinely use notices and legal processes to address unauthorized distribution. What has made this case notable is the reported combination of account identifiers, IP information, phone numbers, linked-account details, device identifiers, telemetry and cloud-storage material, alongside a time window extending back to June 1.

Tom’s Hardware reported that the Microsoft request seeks data for every account that was a member of, or communicated in, the three listed Discord servers during that period, as well as the specifically named handles. The same report says the request seeks MachineGuid values, a Windows identifier generated during installation that Microsoft documentation describes as remaining stable through hardware changes unless the operating-system drive is replaced. Those details explain why the request has been characterised as seeking more than the identity attached to one public-facing handle.

There is a practical investigative logic to requesting linked identifiers. A public alias may be disposable; an account registration record, login address, phone number or linked service can potentially provide a more useful trail. But that does not make every requested category automatically appropriate, available or ultimately produced. The U.S. Copyright Office’s explanation of section 512 says a subpoena under 17 U.S.C. § 512(h) is designed to obtain information sufficient to identify an alleged infringer, to the extent that information is available to the service provider. It also notes that a platform may challenge a subpoena under relevant court rules and the Federal Rules of Civil Procedure.

That legal framework is why Discord’s use of the word “scope” is meaningful. It signals that the platform may consider how closely the requested records relate to the alleged infringement and what the applicable legal process requires. It is not evidence of a future objection, because Discord has announced no such objection. It is, however, a reminder that an issued or requested subpoena does not automatically tell the public exactly which records a service will provide, in what form, or after what internal and legal review.

How a DMCA identification subpoena works

The Digital Millennium Copyright Act is best known by players for takedown notices, but section 512 also contains a mechanism for identifying an alleged infringer. According to the U.S. Copyright Office’s reproduction of the statute, a copyright owner or authorised representative may ask a district court clerk to issue a subpoena to a service provider. The request must include a qualifying infringement notification, a proposed subpoena and a sworn declaration that the purpose is to obtain the alleged infringer’s identity and that the information will be used only to protect rights under copyright law.

The statute states that the resulting subpoena authorises and orders the service provider to disclose information sufficient to identify the alleged infringer, to the extent it is available. The Copyright Office explains that section 512 was designed both to help copyright owners remove infringing material and to provide participating online service providers with liability safe harbors when they meet the statute’s requirements. That architecture is different from a criminal investigation: it is an intellectual-property procedure initiated by the rightsholder, not a public announcement of charges by law enforcement.

That distinction should temper some of the more dramatic claims around the GTA VI story. Take-Two’s reported objective is to identify alleged infringers and protect its copyrighted works. A successful identification request could inform later civil action, additional takedown efforts or referrals, but none of those outcomes follows automatically from the current filings. The materials verified for this article do not show criminal charges, an arrest, a civil damages complaint against the alleged leaker, or a court ruling on anyone’s responsibility for the alleged leaks.

It is also important that DMCA procedure is not a blanket authorisation for a private company to access anything it wants. The statutory language focuses on information sufficient to identify the alleged infringer and on information available to the provider. The Copyright Office further says people seeking to challenge a subpoena should consult local rules and the Federal Rules of Civil Procedure. The exact limits in any individual proceeding depend on the facts, filings, judicial orders and any platform response, rather than on broad assumptions made from social-media summaries.

Microsoft is at a different procedural point

Microsoft’s position differs from Discord’s in one concrete respect: the public docket records an August 21 order directing the clerk to issue the subpoena for Microsoft. Judge Jennifer L. Rochon’s order says the court found good reason to issue an order directing the clerk to issue the requested subpoena. That docket entry is a verified court action, rather than a report based only on a proposed filing.

Microsoft also publicly indicated cooperation. Windows Central reported that Microsoft Chief Technical Officer Scott Van Vliet said on August 21:

“We are working closely with Take-Two and Rockstar Games to support efforts to protect creative works and intellectual property.”

That statement confirms a general posture of cooperation, but it does not disclose what records Microsoft has provided, what it possesses, whether every reported category will be produced, or what conclusions Microsoft has drawn about the alleged leaker.

One detail in the reported request is particularly relevant: Microsoft is described as being approached in its role as GitHub’s service provider, rather than solely through Xbox or OneDrive. The reported predicate notice concerned a GitHub repository, while the request described a wider set of records. That is a reminder that the companies named in a legal process can hold different kinds of data across different services, and that a corporate name in a headline does not identify the specific product or system involved.

For the public, the safe conclusion is not that Microsoft has solved the case. It is that the company has been served with an issued subpoena, the court record confirms issuance, and Microsoft has said it is working with Take-Two and Rockstar to protect intellectual property. Any claim that Microsoft has identified “CyberLeek,” connected a particular device to a particular person, or turned over private files remains unverified in the material available as of August 25, 2026.

A timeline of the verified developments

• June 1, 2026: This is the start of the time period described in reporting on the requested Discord-server records.
• August 20, 2026: Take-Two filed reported DMCA subpoena requests in the Southern District of New York seeking information from Microsoft and Discord in relation to the alleged GTA VI leaks.
• August 21, 2026: The Southern District of New York docketed the Microsoft matter. Judge Jennifer L. Rochon ordered the clerk to issue the requested subpoena for Microsoft.
• August 21, 2026: Microsoft CTO Scott Van Vliet said Microsoft was working with Take-Two and Rockstar Games to support efforts to protect creative works and intellectual property.
• September 4, 2026: Reporting on the filings identifies this as the requested production deadline for Microsoft and Discord. It is a reported deadline, not proof that Discord had been served by August 25.
• August 25, 2026: Discord marketing director Ryan Rigney said Discord had not yet been served by Take-Two and would evaluate validity and scope if service occurred.

The GTA VI context raises the stakes

The intensity of Take-Two’s response is easier to understand in the context of the Grand Theft Auto franchise’s scale, although scale does not answer the separate question of what data collection is justified. Take-Two said in a November 2025 filing that Grand Theft Auto V, released in 2013, had sold in more than 220 million units worldwide. The company said the broader Grand Theft Auto series had sold in more than 455 million units.

Rockstar had already confirmed in February 2022 that active development on the next Grand Theft Auto entry was under way. At the time, the studio said its goal with each new project was to move significantly beyond prior work. The long stretch between numbered entries, combined with GTA V’s enormous audience and the continuing presence of GTA Online, has made official GTA VI news and unverified material alike unusually visible across the internet.

As of August 25, Rockstar’s official GTA VI page lists November 19, 2026 as the game’s launch date and highlights an August 6, 2026 feature titled Grand Theft Auto VI: An Extended Look. Rockstar’s support material also identifies November 19, 2026 as the launch date. Those official sources are the appropriate reference point for release information, not alleged footage, anonymous posts or commentary about supposed builds.

That official-versus-unofficial divide is central to the current situation. Leaked clips, even where rapidly removed or widely discussed, do not provide a dependable representation of the final product. Development builds can be incomplete, altered after capture, wrongly labelled, or shared without their original context. The subpoena story is therefore not a substitute for GTA VI coverage itself: it is a legal and platform-governance story about Take-Two’s response to alleged copyright infringement ahead of a confirmed November release.

What it means for players and community members

For players who simply want to avoid spoilers, the most practical response is straightforward: rely on Rockstar’s official GTA VI channels, avoid repost accounts promising unreleased footage, and do not assume a clip is authentic merely because it is described as removed or “DMCA’d.” The current filings concern alleged infringement and identification efforts; they do not turn all discussion of GTA VI into prohibited activity. But repeatedly circulating unauthorised material can amplify the very distribution that rightsholders are trying to stop.

For members of named communities, the available reporting should not be read as proof of personal exposure or culpability. The request’s reported breadth is precisely why people should avoid naming private individuals, publishing alleged personal data, or treating server membership as evidence. A username, an invitation link or a server appearance in a filing may be an investigative lead or a requested category of records; it is not a judicial finding that every associated person participated in a leak.

For creators and moderators, the episode shows how quickly a community can become part of a copyright dispute even when its central purpose is unrelated to the disputed material. The responsible approach is to remove unauthorised uploads and links where platform rules and copyright notices require it, preserve ordinary moderation records according to applicable policies, and avoid making definitive claims about alleged leakers without verified evidence. The U.S. Copyright Office explains that section 512’s notice-and-takedown structure is built around cooperation with copyright owners while establishing conditions for online-service-provider safe harbors.

What remains unknown

A great deal remains unresolved. The public materials verified here do not establish who “CyberLeek” is, whether the persona refers to one person or several, how any alleged material was acquired, whether Take-Two’s requested data will identify anyone, or whether a future case will be filed against an identified party. They also do not show that Discord has received, challenged or complied with the subpoena as of August 25.

There is also no public, verified basis to say that every element described in reporting will be produced. The Copyright Office’s explanation is clear that the statutory process concerns information sufficient to identify an alleged infringer to the extent available to the provider, while legal challenges to a subpoena are governed by applicable rules. Discord’s stated intention to assess validity and scope underscores that the next step is procedural, not predetermined.

For now, the clearest conclusion is deliberately restrained. Take-Two has escalated its response to alleged GTA VI leaks through federal DMCA subpoena proceedings. Microsoft’s subpoena has been ordered issued, and Microsoft has publicly expressed cooperation. Discord, however, says that as of August 25 it has not yet been served, and it has made no public commitment about the outcome of its review. Until the docket develops or the companies issue fuller statements, that is where the verified story ends.