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.

0cases 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

1 case 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.

1 2025
Reported severity High
More filters: AI relation, use, setting, sources and responses
Clear filters

2 of 707 published cases

Export JSONExport CSV
Jun 2025Event location unknownChatGPT (reported)

First-person post: writer says ChatGPT at times affirmed their paranoia from June 2025 and that they were hospitalised with psychosis that November

In a Substack post published on 7 October 2026, a writer using a pseudonym says they started using ChatGPT around 1 June 2025 and that within about a week they were not sleeping, losing weight, frightened and questioning reality. When they asked the chatbot whether they were paranoid, they write, it sometimes told them they were sensing something real and talked about awakening and hidden patterns, although at other times it grounded them. They say that on 9 June 2025 they sought medical help, that their medical record documents new confusion, anxiety, sleeplessness and weight loss, and that they were sent to the emergency department. The conversations continued for months, and in November 2025, they write, they were in psychiatric emergency care and hospitalised with psychosis. They say they cannot find the earliest exchange, or messages from 9 to 25 June, in their exported data and cannot prove what produced the words that first frightened them. They describe themselves as grounded now. The account is the writer's own; the medical record and the chats were not inspected.

Core concern High reported severity

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 16/10/2026

Event date unknownEvent location unknownChatGPT

Case report: man hospitalised three weeks with bromide poisoning told doctors he swapped table salt for sodium bromide after consulting ChatGPT

A peer-reviewed case report by University of Washington clinicians (Annals of Internal Medicine: Clinical Cases, published online 5 August 2025) describes a 60-year-old man with no psychiatric history who presented fearing his neighbour was poisoning him and was found to have bromism, with a serum bromide level of 1700 mg/L. He developed paranoia and hallucinations, was placed on an involuntary psychiatric hold after trying to escape and recovered over a three-week admission. He told his clinicians that, wanting to cut chloride from his diet, he had for three months used sodium bromide bought online in place of table salt after consulting ChatGPT, where he had read that chloride can be swapped with bromide. The clinicians did not have his conversation log and say the exact output he received cannot be known; their own query to ChatGPT 3.5 produced a reply naming bromide without a specific health warning. No place or date is given.

Core concern High reported severity Media Coverage

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 12/01/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: 16/10/2026. Dataset available under CC BY 4.0.