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
5
Countries with reported events
4
Located 5 of 5 cases · 0 unknown
Languages in checked sources
5
Recorded for 5 of 5 cases

1 case has no reviewed AI-to-person relation yet: 1 not yet reviewed and 0 reviewed as unknown. Show these 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 HighLow
More filters: AI relation, use, setting, sources and responses
Clear filters

5 of 868 published cases

12 Aug 2026ChinaUnidentified chatbot

Rescuers say a man who followed an AI app's suggested route up an undeveloped peak near Hangzhou fell, was stranded at night and had to be rescued

On the evening of 12 August 2026 rescuers were called to Tonggongjian, a peak of about 1,558 metres in the undeveloped mountains of Lin'an district, Hangzhou, where a man who had climbed alone had fallen and was stranded at about 1,300 metres. A volunteer rescue team with police and firefighters, and in the fire service's account its firefighters, found him after more than an hour, with abrasions, and escorted him down. Dushi Kuaibao's report of the rescue says the man had argued with his wife, asked an AI app on his phone where to go, and that the app asked about his state of mind, personality, height and fitness before recommending Tonggongjian; the fire service's account says it suggested he go there to watch a meteor shower. The rescue team said he rarely hiked, wore flat skate shoes and carried only a folding stool, and that the recommendation gave no advice on equipment. The app is not named and the exchange is not published.

Core concern Low reported severity Media Coverage

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

27 May 2026JapanChatGPT (reported)

Nikkei reports two climbers rescued on Yarigatake in Japan's Northern Alps had relied on a ChatGPT answer that light equipment would do

A Singaporean man and a Thai woman became unable to move in rain on a steep slope near Tenguhara, at about 2,400 metres on Yarigatake in the Northern Alps, and asked police for rescue shortly before 5:30 pm on 27 May 2026, according to SBC Shinetsu Broadcasting's report of the police account. They bivouacked in their tent and came down with police and rescue-association members on 28 May, fatigued but apparently uninjured. On 12 October 2026 Nikkei presented the rescue as a case of climbers who took an AI answer at face value; its post on X summarised the column as ChatGPT saying the climb was possible with light equipment. A Vietnamese report (An ninh Thu do, carried by Vietnam.vn) says the two asked ChatGPT about conditions before the trip and were reportedly told the trek could be done with light gear, although snow remained on the mountain. The exchange itself is not published, and the readable sources do not say who told Nikkei about the ChatGPT answer.

Core concern Low reported severity Media Coverage

AI involvement reported · Causal attribution alleged · 4 sources, 2 underlying accounts · Added 14/10/2026

4 Jul 2026PolandChatGPT (reported)

TOPR says two Lithuanian hikers followed an AI assistant's shortcut suggestion into climbing terrain in the Polish Tatras and were evacuated by helicopter

The Tatra Volunteer Search and Rescue service (TOPR), summarising a busy first week of July 2026, told the Polish Press Agency that two tourists from Lithuania became stuck below Niebieska Turnia in the Polish Tatras. According to the TOPR duty rescuer, as relayed by RMF24 and Onet, the pair wanted to shorten their way to the Valley of Five Polish Lakes and used suggestions from an artificial-intelligence assistant, which pointed them across Świnicka Ławka; they ended up in difficult climbing terrain and were evacuated by helicopter. TVN24's reporter said the event happened at the start of July, that the hikers were using 'one of the popular AI models', that good weather let rescuers locate them quickly and that they were flown to Zakopane. TOPR's own report of 10 July lists the call among its afternoon entries for 4 July, as LRT also reported on 13 July, and says the pair had used ChatGPT's advice ('porad czatu GPT'); the PAP relays name no product, and the hikers' exchanges with the assistant have not been published. No injury is reported.

Core concern Low reported severity Media Coverage

AI involvement reported · Causal attribution supported · 6 sources, 2 underlying accounts · Added 10/10/2026

29 Aug 2026 to 31 Aug 2026United StatesGemini

Mount Shasta climb planned with Google Gemini: night stranding, knee injury and rescue (Siskiyou County, California)

Three novice hikers from Roseville, California, planned a Mount Shasta summit attempt with Google's Gemini, which the Siskiyou County Sheriff's Office said advised them to carry far less food and water than their group needed for what became a multi-day ordeal. After reaching the summit at 7 p.m. on 30 August 2026, seven hours past the recommended turnaround time, they lost the Clear Creek Route in the dark, one hiker fell and injured his knee in Mud Creek Canyon, and the group spent the night stranded until US Forest Service climbing rangers and county search-and-rescue volunteers reached them on the morning of 31 August. The sheriff's office called the reliance on Gemini 'a critical misstep'.

AI relation under review Low reported severity Media Coverage

Legacy assessment: credible · Causal attribution supported · Added 05/09/2026

5 Apr 2025United StatesGemini

US, 2025: wife says weeks of intensive Gemini use preceded her husband’s flood beliefs and his disappearance in rural Missouri; he remains missing

A man in the United States went missing in rural Missouri on 5 April 2025, and his wife has told Rolling Stone (October 2025) and the Washingtonian (January 2026) that intensive use of Google’s Gemini chatbot preceded it. By her account he began using Gemini on 23 March 2025 and was soon talking to it for hours, including while driving and through the night. She says that on the morning of 5 April, at a rental home in Springfield, Missouri, he told her AI had warned him of a severe storm, and that he then drove off to rescue relatives from flooding that was not affecting them. Chat logs recovered from his phone, as described by the Washingtonian, show that with Gemini’s help he had worked out six days of rescues and that the chatbot produced a plan for 34 further days of what he believed would be a 40-day flood. Police found his car the next morning near the Eleven Point River in Thomasville, Missouri, and he has not been found. His wife believes he would not have gone missing without the chatbot. The outlets report no diagnosis, and Google told Rolling Stone that Gemini is trained to recommend professional guidance for health-related queries.

Core concern High reported severity Media Coverage

AI involvement reported · Causal attribution alleged · 3 sources · Added 25/08/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.