Skip to main content

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

In this selection

Published cases
2
Countries with reported events
1
Located 2 of 2 cases · 0 unknown
Languages in checked sources
1
Recorded for 2 of 2 cases

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.

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

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.

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

2 of 1101 published cases

17 Jul 2026United StatesUnidentified voice-cloning tool

Boone County, Missouri: sheriff's office says a fake-kidnapping ransom call used an AI-generated copy of a resident's daughter's voice

The Boone County Sheriff's Office in Missouri said that on Friday 17 July 2026 a resident received a call whose caller ID showed their daughter's number. A voice that sounded like the daughter said she had been kidnapped at gunpoint, and another voice then demanded ransom. The office said it later determined that the voice was AI-generated, without saying how. Deputies found the daughter safe in Jefferson City and unaware of the call. The office called it the first AI voice-impersonation call it had encountered. No suspect had been identified by 19 July, and no source reports whether any money was paid.

Core concern Low reported severity Investigation Opened

AI involvement reported · Causal attribution supported · 3 sources, 1 underlying account · Added 15/10/2026

10 Feb 2026United StatesChatGPT

Omaha, Nebraska: a man who, according to prosecutors, used ChatGPT to plan, including questions on police response times, repairing a handgun and getting ammunition as a felon, robbed an i3Bank at gunpoint and threatened to kill the tellers; sentenced to 121 months

On 10 February 2026 a 23-year-old man walked into the i3Bank in Omaha, pointed a gun at the tellers, threatened to kill them unless they handed over cash without dye packs, and left with about $9,175. According to the prosecutor's statement relayed by WOWT and heise, a consented search of his phone showed he had used ChatGPT to plan the robbery, asking about law enforcement response times, how to strip and repair a Llama Mini-Max .45 handgun, and how to obtain ammunition as a felon; his Google Maps history showed directions to the bank. He was sentenced in federal court on 13 August 2026 to 10 years and one month in prison. No source quotes what ChatGPT answered.

Core concern Medium reported severity Criminal Charges

AI involvement reported · Causal attribution unclear · 2 sources, 1 underlying account · 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: 11/11/2026. Dataset available under CC BY 4.0.