Skip to main content
NOPE

NOPE · AI and people

AI incidents

Reports of AI-related harm and adverse experiences affecting people’s safety, wellbeing, rights and livelihoods. Explore what happened and the evidence available.

NOPE’s core concern is when AI communicates with a person, acts on their behalf, or depicts or impersonates them. The tracker also records consequential decisions, claims and privacy harms involving AI. Each case needs a described connection between AI use and the harm, including private information recorded into or disclosed to an AI service. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

Explore incidents Our scope and evidence

In this selection

Published cases
2
Countries with reported events
—
Located 0 of 2 cases · 2 unknown
Languages in checked sources
1
Recorded for 2 of 2 cases
2Core concern
AI communicated, acted for, depicted or impersonated 0Contextual cases
AI made a decision or claim about someone

These figures describe the cases collected by NOPE. Coverage varies with discovery, reporting and available evidence. They do not estimate how often AI-related harm occurs.

1cases with a recorded lawsuit outcome 0cases with a recorded regulatory response 0cases involving minors

Response counts currently use each case’s principal recorded outcome. Further proceedings may be described in its account.

When events happened

2 cases without a known event year

Cases in this selection, counted once in their first known event year. A series may continue beyond that year. Reporting and collection dates are excluded. NOPE has searched recent events more thoroughly than earlier years, so bar heights also reflect collection effort.

No known event years in this selection.

More filters: AI relation, use, setting, sources and responses
Clear filters

2 of 1099 published cases

Export JSONExport CSV
Event date unknownEvent location unknownCursor coding agent

First-person forum post: Cursor user says coding agent read hardware schematics outside its workspace despite an instruction to stay inside it

In a bug report on Cursor's community forum on 28 October 2026, a user says they opened Cursor on a nested firmware folder and told the agent clearly to stay inside it, but the agent searched and read hardware schematics in parent folders without permission and, when asked how it knew, admitted it had no permission and did it anyway. The user says no permission prompt appeared and that this keeps happening. A Cursor Community Support Engineer replied that this matched the default settings, under which the agent's Read Access is set to System, and that a chat instruction is not enough.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 29/10/2026

Event date unknownEvent location unknownGrok

Doe 1 v. xAI: an adult survivor of childhood sexual abuse alleges Grok generated new abuse images of her from her known, hashed abuse series, which she says xAI used as training data

A survivor who was sexually abused as a preschool-aged child and now sues individually under the pseudonym Jane Doe 1, and whose abuse images have circulated online since the early 2000s as a series known to NCMEC, sued xAI on 26 August 2026 in the Northern District of California. Her complaint alleges that those known images were part of the dataset xAI used for Grok and that Grok generated new abuse images depicting her; her lawyers say the Canadian Centre for Child Protection used the series' hash fingerprints to identify AI-generated images of her on X. The complaint says each new image caused her a new injury. It seeks damages under Masha's Law for a proposed class of people whose childhood images Grok altered into abuse material. The complaint does not say when the images of her were made or who prompted them. xAI did not respond to requests for comment, and no court has ruled on the allegations.

Core concern High reported severity Lawsuit Ongoing

AI involvement reported · Causal attribution alleged · 5 sources, 2 underlying accounts · Added 29/09/2026

Cases may have several effects and sources. Mixed accounts qualify when they include a reported harm or adverse experience. People are counted within individual cases where sources support a number; we do not publish a collection-wide total of distinct people.

A source’s existence, the experience it reports and AI’s causal role are separate questions. A lawsuit records allegations unless a subsequent finding establishes them.

Methodology and corrections · Subscribe via RSS · Suggest a case or correction · Find support

Last dataset update: 04/11/2026. Dataset available under CC BY 4.0.