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
4
Countries with reported events
2
Located 2 of 4 cases · 2 unknown
Languages in checked sources
2
Recorded for 4 of 4 cases
4Core concern
AI communicated, acted for, depicted or impersonated 0Contextual cases
AI made a decision or claim about someone

1 case has no reviewed AI-to-person relation yet: 0 not yet reviewed and 1 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.

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

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.

2 2025
Reported severity CriticalLow
More filters: AI relation, use, setting, sources and responses
Clear filters

4 of 868 published cases

Export JSONExport CSV
28 Jun 2025EgyptDeepSeek

Case report: man self-treated with colchicine after a DeepSeek dialogue pointed to a rare fever syndrome; liver enzymes rose before specialist review

Clinicians at the University Medical Center Hamburg-Eppendorf report in EULAR Rheumatology Open (published 29 September 2026) a man in his thirties with nearly three decades of unexplained febrile attacks who, in a dialogue with DeepSeek begun on 28 June 2025, saw the model's differential narrow to familial Mediterranean fever (FMF). The authors write that the model repeatedly recommended specialist assessment but also discussed a diagnostic trial of colchicine with specific dosing. Motivated by the hypothesis, he arranged commercial genetic testing and obtained colchicine from a pharmacy in Egypt, starting it without specialist supervision. His attacks stopped, but his alanine aminotransferase rose to 160 U/L and colchicine was paused and later resumed at a lower dose. FMF was confirmed when he presented to the clinic in February 2026. The authors write that the case illustrates how patient-facing models may facilitate recognition of rare autoinflammatory diseases, and that confident diagnostic language combined with actionable treatment advice may also encourage unsupervised testing and self-medication.

Core concern Low reported severity Media Coverage

AI involvement reported · Causal attribution alleged · 1 source · Added 12/10/2026

Event date unknownEvent location unknownCline

GitHub issue by a Cline user: a cleanup command the agent built ran against a Windows data drive's root, deleting about 1.5 TB of personal files, user says

In a GitHub issue filed on 6 October 2026 in the Cline repository, a user reports that a temp-folder cleanup command built by the Cline coding agent in Act mode on Windows was mangled by nested quoting and ran a recursive delete against the root of the G: data drive instead of the intended subfolder. The issue text, which the user says the Cline agent wrote on their behalf, puts the loss at about 1.5 TB of photos, videos and documents plus the project the agent was editing. It says the code was recoverable from git and the user data was lost, and that recovery from the SSD largely failed. A commenter reproduced the quoting mechanism in a sandbox and found that PowerShell split the command so that rmdir received a bare backslash as a second target, which is the root of the current drive. One contributor proposed an Act-mode guard. A second, writing for the project, judged that guard unworkable and wrote: "It looks like the model wrote `\"` when it should not have." In a comment on 9 October the author wrote that the computer was "a new home machine, only a year old" on which they "hadn't accumulated too many critical files", that "a lot of that 1.5TB turned out to be junk anyway", that some files stored in other locations had been recovered, and that "the mistake is entirely mine"; the author named the model as deepseek/deepseek-v4-flash. The loss itself rests on the user's account.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 07/10/2026

Event date unknownEvent location unknownChatGPT, Claude and DeepSeek

Developer reports workload pressure during AI-assisted programming

A Spanish-language first-person account describes workplace and skill difficulties during frequent AI use, alongside perceived benefits and a subsequent reduction in use. The account remains uncorroborated.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 15/09/2026

23 Oct 2025 to 24 Oct 2025United KingdomDeepSeek (reported)

Prosecutor reports DeepSeek advice before a man murdered his mother in Wales

A man murdered his mother in Wales after an attack spanning 23–24 October 2025, as established in the sentencing remarks. At the sentencing hearing, the prosecutor reportedly said DeepSeek first refused a violent request, then supplied advice after it was reframed as fiction. The judgment confirms the murder and internet research but does not mention AI. The role of DeepSeek remains an attributed prosecution account.

Core concern Critical reported severity Criminal Charges

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 03/06/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.