AI Risk Wire

Cases › produced harmful content › LR-2026-0485

Dutch court orders Grok to stop generating non-consensual nude images

Preliminary Why: Publisher not yet named · subject to change

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 26 Mar 2026
Developer and model xAI · Grok

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

Severity major: Regulator-involved test met: Ireland's Data Protection Commission, the European Commission and Ofcom have opened enforcement actions.

Grok, the AI chatbot developed by xAI and offered on the X platform, included an image editing feature that could generate sexualized images of real people without their consent, including child sexual abuse material. Offlimits, an expertise center on online sexual abuse, sent a formal notice on 4 February 2026 demanding the functionality stop. At a 12 March hearing, xAI's lawyers argued that stringent safeguards had been in place since 20 January 2026. Offlimits presented evidence that on 9 March 2026 it could still generate a sexualized video of an existing person from a single photograph without consent verification. The Amsterdam District Court issued a binding injunction, with daily penalties of €100,000 per defendant for non-compliance, ordering xAI, X Corp and X Internet Unlimited Company to stop the prohibited generation and distribution in the Netherlands.

What happened

1 · What it was doingGrok's image editing feature launched in late December 2025, and reports of sexualized imagery to Offlimits surged.
2 · What went wrongOn 9 March 2026 the court found that a sexualized video of an existing person could still be generated from one photo without consent verification.
3 · What it reached or didA CCDH report estimated about 3 million sexualized images generated between December 29, 2025 and January 8, 2026.
4 · How it was caughtOfflimits and Fonds Slachtofferhulp brought the case after concluding that regulatory enforcement was too slow.

What was done

The Amsterdam District Court ordered an immediate stop to the prohibited generation in the Netherlands, with daily penalties for non-compliance.

Risks

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

Read from the sources; not yet reviewed by a person.

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: 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: 10 items from the primary sources

What happened, in order

  1. late December 2025 Grok's image editing feature launched.
  2. December 29, 2025 to January 8, 2026 CCDH estimated Grok generated approximately 3 million sexualized images in this period, including an estimated 23,000 appearing to depict children.
  3. January 2026 The European Commission launched DSA proceedings against X.
  4. 2026-01-20 xAI's lawyers later said stringent safeguards had been implemented as of this date.
  5. February 2026 Ireland's Data Protection Commission opened a GDPR investigation.
  6. 2026-02-04 Offlimits sent a formal notice to xAI and X demanding they cease the functionality.
  7. 2026-03-09 Offlimits was still able to generate a sexualized video of an existing person from a single uploaded photograph without Grok verifying consent.
  8. 2026-03-12 At the hearing, xAI's lawyers argued that safeguards were in place and categorically rejected any suggestion that Grok still permitted such content.
  9. 2026-03-16 Civil suits were filed in the United States, including by three Tennessee teenagers.

Not dated in the sources:

  • The defendants have ten working days from service of the judgment to confirm compliance in writing.
Show every field, with its source and grade

The AI system

Model
Grok
C one secondary source states it
Developer
xAI
C one secondary source states it

What happened

Earliest source we hold
2026-03-26
D inferred by us from the described behaviour, reason shown
Who caught it
an outside party
C one secondary source states it
Themes
non-consensual imagery, child sexual abuse material, court injunction
C one secondary source states it
Who was responsible
the model provider
C one secondary source states it
Earlier warning signs
Formal notice to xAI and X on 2026-02-04 demanding they cease the functionality; reports to Offlimits had surged after the feature launched
C one secondary source states it
What went wrong
produced harmful content
C one secondary source states it
primary risk
RK12
D inferred by us from the described behaviour, reason shown
secondary risks
RK15
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown
Kind of harm
privacy
C one secondary source states it
Who was affected
Persons residing in the Netherlands depicted in sexual imagery without explicit consent, and children depicted in child pornographic material
C one secondary source states it
Why this severity
Regulator-involved test met: Ireland's Data Protection Commission, the European Commission and Ofcom have opened enforcement actions.
D inferred by us from the described behaviour, reason shown

Context

Country
Netherlands
C one secondary source states it

Notes on gaps

No source states a single date of occurrence; the harm period is a CCDH estimate range and the feature launch is given only as late December 2025. The CCDH counts are estimates reported by a press source and are not verified.

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