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
3
Countries with reported events
2
Located 2 of 3 cases · 1 unknown
Languages in checked sources
3
Recorded for 3 of 3 cases
2Core concern
AI communicated, acted for, depicted or impersonated 1Contextual 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 1cases 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.

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

3 of 868 published cases

Export JSONExport CSV
2026IsraelChatGPT (reported)

Mother tells Ynet she waited two days after ChatGPT, while advising a check, said it was relatively rare; her teenage son lost a testicle

Ynetnews reported on 12 April 2026 that doctors at Meir Medical Center had seen three teenage boys lose a testicle in the past month after arriving too late for treatment of testicular torsion. The mother of one of them told Ynet that when her son complained of lower abdominal pain she thought it might be constipation and consulted ChatGPT, which gave several options, said it could be something serious and that they should get it checked, but also said it was relatively rare, so they thought they could wait. After two days without improvement the boy's testicle was swollen and he could hardly walk; an urgent care clinic sent them to hospital and ChatGPT, consulted again, told them to go to the emergency room immediately. At the hospital, late at night, doctors diagnosed severe torsion, operated and removed the testicle; the boy is recovering at home. The doctors attribute the month's unusually high rate of complications mainly to delayed arrival at the emergency room, which they say the war has partly influenced.

Contextual tracker case High reported severity Involving minors Media Coverage

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

Event date unknownRussiaUnidentified video tool

SHOT reports Moscow woman hospitalised after following advice from a persona it describes as AI-generated

SHOT reports that an older Moscow woman followed a health recipe from a social-media herbalist whom she believed was a real person. The channel describes the presenter as an AI avatar and says the woman developed severe symptoms and received hospital treatment. Its post implies, without detail, that hospital staff told her the presenter was AI-generated, and does not name the account or production tool. Glavny.tv, relaying SHOT, reports that she recovered. This is one unverified reporting chain. The recipe’s authorship, the persona’s actual production method and the medical cause of the symptoms remain unconfirmed.

Core concern Medium reported severity

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