AI Risk Wire

Cases › produced harmful content › LR-2026-0458

Teen plaintiffs sue xAI over Grok-generated child sexual abuse images

Confirmed Why: 2 independent outlets · 2 independent reports

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: action reported, no fix

Severity major
Reported 16 Mar 2026
Developer and model xAI

No source states: loss or records, agent tool, could do, deployer, industry.

Grok is xAI's image generator, and it is the subject of a proposed class action filed by three Tennessee teenagers and their guardians. The complaint alleges that photos of the girls were altered into nude images and shared on a Discord server. It further alleges that police found child sexual abuse material on a suspect's phone, produced using xAI's technology through a third-party app. Earlier, researchers estimated that Grok generated about three million sexualized images, around 23,000 depicting children, and xAI had refused to update filters to block nudifying images of real people. The plaintiffs seek an injunction and damages. xAI did not immediately respond to a request for comment. The allegations are unproven.

What happened

1 · What it was doingPlaintiffs allege that xAI's Grok image generator was used to turn photos of them into child sexual abuse material and distribute it.
2 · What went wrongThe complaint alleges the material was made through a third-party app that licensed and relied on Grok's AI.
3 · What it reached or didAccording to the complaint, the images were shared on Telegram, where they were allegedly used to barter for more such material.

What was done

The plaintiffs have asked a US district court for an injunction and seek damages, including punitive damages, for all minors harmed.

Risks

Harmful content and jailbreaks
Primary
84 incidents
Rising: 6 vs 3.8 a week

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Model

Safety training and refusal · Content safety classifiers · Abuse monitoring and account enforcement · Outside red-teaming

Application

Output filtering and redaction

Similar incidents

All cases of this kind ›

Evidence

No source states: how it was caught, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.

Show the full account: 3 items from the primary sources

What happened, in order

  1. January Musk denied that Grok generated any CSAM during the scandal.
  2. February The other plaintiffs discovered that similar material featuring them had been generated and shared online.
  3. December One plaintiff received an anonymous Instagram message alerting her that images of her had been uploaded to a Discord server.
Show every field, with its source and grade

The AI system

Developer
xAI
C one secondary source states it

What happened

Earliest source we hold
2026-03-16
D inferred by us from the described behaviour, reason shown
What went wrong
produced harmful content
C one secondary source states it

Impact

Severity
major
D inferred by us from the described behaviour, reason shown

Notes on gaps

All harm claims are allegations from a complaint and press reports; no court finding or xAI response is in the sources. Date of occurrence is not stated as a single date (December, January and February are given for different events). The third-party app is not named. Control C5 failed is taken from the report that xAI refused to update filters; no other controls are stated as held, failed or bypassed.

LR-2026-0458 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON