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 is wider: it also records consequential decisions and claims about people. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
3
Countries with reported events
1
Located 2 of 3 cases · 1 unknown
Languages in checked sources
2
Recorded for 3 of 3 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

3 of 425 published cases

2 Jan 2026Event location unknownGrok

UK: Grok-made sexualised images of a Welsh presenter and campaigner against deepfake abuse and of a commentator and broadcaster, requested by anonymous X accounts around New Year 2026; South Wales Police and the Metropolitan Police closed their investigations without identifying a suspect after X did not answer information requests; the presenter is in pre-action correspondence with xAI

The Bureau of Investigative Journalism and The Observer reported on 29 September 2026 that police investigations into sexualised images generated by X's chatbot Grok had failed to identify anyone. A Welsh presenter and campaigner against deepfake abuse, who had criticised Grok publicly on New Year's Eve 2025, saw an anonymous X user ask '@grok' to put her in a bikini made of cling film; Grok generated the image from her profile photo and posted it. She reported it to South Wales Police on 2 January 2026, was not asked for a statement until March, and was told officers had not heard back from X; the case was closed (in May, per The Observer) with the force saying no suspect could be identified. The same account also targeted a commentator and broadcaster, who estimates about 300 Grok images and videos of her were posted during the wave, including one alongside Jeffrey Epstein reported to the Metropolitan Police, which likewise said no suspect could be identified. The presenter is now in pre-action legal correspondence with xAI (part of SpaceXAI) alleging misuse of private information and breaches of data-protection law and the Equality Act; the company told her lawyers it had not been possible in the time available to look into its communications with South Wales Police. BBC Wales had reported in January 2026 that explicit images of the presenter were created with the chatbot and shared without her consent.

Core concern Medium reported severity Investigation Opened

AI involvement supported · Causal attribution supported · 3 sources, 2 underlying accounts · Added 30/09/2026

17 Apr 2026 to 19 Apr 2026ChinaDoubao

Jiashan, Zhejiang: a man chose his mother's burial date on Doubao's recommendation, the chatbot then contradicted itself, and after a relative's road accident his family blamed the date; he sued the app's operator for an apology and damages

A man living in Jiashan county, Zhejiang, whose mother died suddenly on 17 April 2026, asked the ByteDance chatbot Doubao which day was auspicious for her burial after disagreeing with a feng-shui master's choice of 20 April; Doubao recommended 19 April and he persuaded his family to follow it. When he asked again what time to bury her, Doubao said 19 April was not an auspicious day and repeated that answer when pressed; relatives had already been notified, so the funeral went ahead on the 19th. Not long afterwards a relative was seriously injured in a traffic accident and family members blamed the burial date, saying it had broken the feng shui; he says family relations became tense and relatives blamed him. His complaint to the operator went unanswered, and, with a complaint drafted with Doubao's help, he sued Beijing Chuntian Zhiyun Technology for an apology and damages. Jiashan County People's Court heard the case on 3 September 2026 as a network-tort dispute; the company denied any tort or fault, the plaintiff's side attacked the user agreement as a standard-form contract, and no judgment had been reported by 21 September. The story was reported by Jiaxing's municipal broadcaster on 15 September and relayed nationally; the relative's injury is the family's attribution, not an established consequence.

Core concern Low reported severity Lawsuit Ongoing

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

10 Jul 2026ChinaUnidentified chatbot

Chuzhou, Anhui: a 67-year-old farmer sprayed 150 mu of sesame by drone with an AI assistant's 'weeding and pest-control plan' that named a soybean-field herbicide; the seedlings died overnight

On 10 July 2026 a 67-year-old farmer in Chuzhou, Anhui, who said he had relied on an AI assistant app for more than a year for questions such as when to spray and fertilise, asked it for a weeding and pest-control plan for his sesame field and then for a drone-spraying version. The app produced a 'full plan for 100-mu sesame aerial weeding and pest control' recommending the herbicides haloxyfop-P-methyl (高效氟吡甲禾灵) and fomesafen (氟磺胺草醚) and two insecticides. He sprayed the whole 150-mu field; the next day grass and seedlings had died together. A nearby pesticide dealer and an agronomist told Lizhi News (Jiangsu Broadcasting) that fomesafen is a broadleaf herbicide for soybean fields that must not be sprayed on sesame, and that spraying it across a whole field kills the crop; asked afterwards, the app itself said fomesafen was the cause. The chat window carried a small header line saying AI output may be wrong and should be verified, which he said he had never noticed. The app's customer service said the software has no knowledge base of its own and assembles answers from public web content, and logged the loss for follow-up; no reply or compensation was reported by publication on 1 August 2026. Relays put the loss at about 150,000 yuan; that figure is not in the text of the originating report.

Core concern Medium reported severity Media Coverage

AI involvement supported · Causal attribution supported · 4 sources, 3 underlying accounts · Added 20/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: 01/10/2026. Dataset available under CC BY 4.0.