A new Grok class action drags the training corpus into discovery
Earlier suits over Grok's nudify feature asked why xAI lacked its competitors' safeguards. This one asks what the model was fed, and asks the court to destroy anything that could feed it again.
The Product Desk
What happened
- A proposed class action filed Wednesday by a plaintiff known as Jane Doe accuses xAI of training Grok on child sexual abuse material, according to Ars Technica.
- Government probes, individual lawsuits and at least three earlier class actions had already followed the wave of Grok-made sexual deepfakes, Gizmodo reports.
- Those earlier cases argued that xAI failed to install safeguards its competitors already have, and this is the first to allege the company trained its models on the material.
- Beyond damages, the complaint asks the court to order destruction of all Grok-generated CSAM, including copies that could be used to train the models.
Why it matters
- Who's exposed exposure A training-data theory puts ingestion records and retention policy inside the discovery envelope for any team shipping image generation, where moderation logs used to be the whole of the answer.
- What it limits constraint If the persistence argument survives, taking images down stops functioning as a complete remedy, and a team owes an account of the checkpoints trained after the material arrived.
- Who has to decide decision Recycling your own outputs back into training becomes a setting someone has to justify in writing rather than a free source of data, because the growth reasoning behind it reads as intent in a complaint.
- What it sets up precedent The first complaint aimed at the corpus rather than the filter makes provenance the obvious second count for plaintiffs' firms in the next suit, whatever happens to this one.
Next story · Invest · 3d ago
SpaceX accepts the NYC Council's AI subpoena after a threat of court enforcementConfirmed2 publishers
The mechanism in the filing is a loop. Gizmodo, reading the complaint, reports that xAI policy treats anything posted publicly on X and any output Grok produces as training-eligible, so an image that survives on the timeline for even a short window becomes a candidate row in the next corpus [20]. Output moderation, the part most teams actually instrument and report on, sits downstream of that. It removes the artifact and leaves the ingestion decision untouched.
The persistence argument is where this lands on engineering rather than trust and safety. The complaint says that once such material entered training, its influence likely persists into future outputs, so the harm is not resolved by removing individual images or unposting them [10]. Deleting a file is a ticket. Producing an account of which checkpoints were trained after the material arrived is different, harder work, and most teams have never been asked for it.
The provenance question here is not exotic. Doe was preschool-age in the early 2000s when men raped her to make CSAM for sale online, according to her complaint [2], and her images were hashed afterward by the National Center for Missing and Exploited Children and the Canadian Centre for Child Protection [3]. The filing describes material that has followed her more than 20 years [4], which puts roughly two decades of hash coverage ahead of the AI-generated versions the CCCP told her it had identified on xAI [17]. Sarah London of Girard Sharp, Doe's counsel, put the claim in terms of knowing training on survivors' abuse images [15].
A product deck might describe users of a generation feature as prompting, looking, and discarding. The record in these filings describes something else. Musk promoted the nudify capability himself, millions of nonconsensual sexual deepfakes went onto the X timeline, and a large share of the victims were children [12]. Ars Technica reports the complaint citing forum messages between offenders discussing how to make AI CSAM of Doe and other known earlier victims [8]. The growth rationale is now an exhibit: the complaint alleges Grok was built to answer sexual-content prompts in order to entice more users of both X and Grok [14].
The two publishers describe her notification path differently. Gizmodo says Doe is tracked by the FBI's Child Exploitation Notification Program [c19a]; Ars says she opted into alerts from the Justice Department's Victim Notification System [c2b]. Neither has seen a corpus, and both are describing the same complaint.
xAI has said, in its own suit against two users who made CSAM with the tool, that it helped arrest at least 244 people who created or distributed such material through Grok [6]. Counting to 244 requires records of what was produced. That is the shape of the forcing function for anyone shipping image generation next quarter: take one image your product removed last month, and see whether you can name the training runs that saw it and say what became of the checkpoints trained afterward. Answering the first question means you have logs; answering both means you have provenance, which is what this complaint is asking about [9].
What to watch
- Whether xAI answers the training-data allegation on the merits or moves to dismiss that count separately.
- Whether any remedy the court entertains reaches model checkpoints rather than stored files.
- Whether the earlier Grok class actions amend to add a training-provenance count of their own.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence45
- Adoption60
- Hype gap+22
- Incentives74
- Confidence57
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
A complaint filed on Wednesday accuses xAI of training Grok on child sexual abuse material (CSAM), brought by a plaintiff known as Jane Doe.
- [2]
Doe's complaint states she was preschool-age in the early 2000s when adult men repeatedly raped her to create CSAM to sell to pedophiles online.
- [3]
Since then, Doe's images have been hashed by groups including the National Center for Missing and Exploited Children (NCMEC) and the Canadian Centre for Child Protection (CCCP).
- [4]
Doe's complaint describes images that have haunted her for more than 20 years, and she believes Grok was trained both on that initial set and on the more recent AI-generated ones.
- [5]
Numerous government probes, individual lawsuits, and at least three class actions followed the wave of Grok-made sexual deepfakes.
- [6]
xAI sued two of its own users who used the tool to create CSAM, and in that complaint claimed to have helped arrest at least 244 individuals who created or distributed CSAM content via Grok.
- [7]
The CCCP notified Doe that it had identified AI-generated CSAM on xAI that depicted her.
- [8]
The complaint alleged that messages were found on online forums between offenders chatting about creating AI-generated CSAM of the plaintiff and other similarly situated known, legacy victims of CSAM.
- [9]
All legal action against Grok so far had focused on holding xAI accountable for failing to put up safeguards its competitors already have; this lawsuit is the first to accuse the company of training its models on the CSAM it produces.
- [10]
The complaint states that as long as Grok retains the capability to generate this content the harm cannot be considered resolved just because individual images are removed or no longer posted publicly, and that if such material entered training its influence likely will persist and contribute to future abusive outputs.
- [11]
The plaintiff asks the court to award damages to victims whose photos were allegedly used to generate CSAM and requests the destruction of all Grok-generated CSAM, not just publicly existing images but any that could be used to train its models.
- [12]
Musk personally promoted Grok's ability to nudify photos on his X account, after which millions of nonconsensually created sexual deepfakes flooded the X timeline, and a bulk of the nudification victims were children.
- [13]
Musk limited who could use the nudification feature by putting it behind a paywall, and the so-called spicy mode feature is still available though more restricted.
- [14]
The complaint claims xAI intentionally designed Grok to respond to user prompts to create sexual content in an attempt to entice more users of both X and Grok.
- [15]
Sarah London, the plaintiff's counsel and a partner at Girard Sharp, said in a press release that xAI must be held responsible for knowingly training its models on images of the horrific abuse she suffered and on the abuse images of every other survivor in the class.
- [16]
Margaret E. Mabie of Marsh Law Firm, also plaintiff's counsel, said there is no artificial intelligence exception to federal child protection laws.
- [17]
Roughly two decades of NCMEC and CCCP hash coverage of Doe's images preceded the AI-generated versions identified on xAI.
- [18]
For her safety, Doe opted to receive alerts from the US Department of Justice Victim Notification System any time she may be a victim in a new criminal investigation.
- [19]
Gizmodo reports that the plaintiff is a previous victim of child pornography who is tracked by the FBI's Child Exploitation Notification Program.
- [20]
According to the lawsuit, xAI policy treats anything posted publicly on X and any output generated by Grok as training-eligible content, meaning every piece of CSAM posted by Grok was automatically fed back into the chatbot to refine it.
Sources
2 independent publishers whose own reporting we read for this story.
- arstechnica.comElon Musk’s xAI used child porn to train Grok models, lawsuit says
1 article · August 27, 2026
- gizmodo.comGrok Not Only Generates Child Porn but Was Also Trained On It, New Lawsuit Claims
1 article · August 28, 2026
Topics and entities
Topics
- Nonconsensual generative deepfakes
- Trust and safety enforcement
- CSAM and online child safety
- AI litigation and liability
- AI Training Data Provenance
Entities
- FBI Child Exploitation Notification Program
- National Center for Missing and Exploited Children
- Canadian Centre for Child Protection
- US Department of Justice Victim Notification System
- Elon Musk
- Margaret E. Mabie
- Grok
- X
- xAI