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
479
Countries with reported events
47
Located 262 of 479 cases · 217 unknown
Languages in checked sources
38
Recorded for 479 of 479 cases

41 cases have no reviewed AI-to-person relation yet: 1 not yet reviewed and 40 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 CriticalHighMediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

479 of 1102 published cases · page 15 of 24

3 Oct 2026 to 4 Oct 2026IndiaUnidentified video tool

Delhi Police say a ‘CCTV’ reel of a named ACP molesting a woman journalist at a protest was AI-generated; Haryana man arrested, her allegation unresolved

Delhi Police said at a press conference on 6 October 2026 that a reel circulated on Instagram and Facebook on 3–4 October, presented as CCTV footage, showed a person dressed as a police officer behaving inappropriately with a woman, with the photograph, name and designation of ACP Vivek Bhagat (Connaught Place) displayed so that it appeared to show him. According to the police, the man who ran the page used AI tools to generate the footage, a police technical test confirmed the clip was AI-generated, and he confessed to making it to malign the force; they also said its circulation caused agitation among protesters. A man from Palwal, Haryana, who runs an Instagram news page was arrested in the Mewat region on 5 October and booked for forgery, public mischief and attempting to provoke a breach of the peace. Separately, a woman journalist covering the 3 October protest against the Chief Election Commissioner had complained that the same officer groped and shoved her; ThePrint reported that no FIR had been filed against the officer and that no proof other than the purported footage had emerged; India Today reported that the Crime Branch was examining complaints by three women journalists. All statements about the video’s origin are the police’s; no independent forensic examination is reported.

Core concern Medium reported severity Criminal Charges

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

Event date unknownEvent location unknownClaude Code (reported)

Software tester says their employer made them redundant, telling them it uses AI and Claude Code more heavily and needs fewer QA staff (first-person account)

In a public post to r/AskUK created on 6 October 2026, a person who describes about eight years of work as a software test engineer writes that they have just been made redundant. They say the reason given was that the company is using AI and Claude Code more and more heavily, that its testing and development processes are changing, and that it no longer needs many of its QA staff, adding "So I'm told". In replies the poster says their own job had consisted of writing automation code and debugging with Claude, and that the redundancy also affected the company's developers. The employer, its location and the date of the redundancy are not stated. The account is the poster's alone and uncorroborated; no statement from the employer was retrieved.

AI relation unknown Medium reported severity

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

30 Sept 2026Event location unknownGoogle Antigravity (suspected)

First-person forum post: Antigravity user says about 120 GB, including a month of client work, vanished during a disk-cleanup session the agent ran

In a post on the Google AI Developers Forum dated 30 September 2026, filed in the Google Antigravity category, a Windows laptop user says they asked the agent to free space on a full C: drive. By their account the agent deleted a folder of about 50 GB of recovered videos and turned off hibernation, they then asked it to turn hibernation back on, their internet connection dropped while it was working, and when they returned their files, Desktop and Antigravity conversations were gone, with free space up from about 50 GB to 172 GB. They estimate roughly 120 GB deleted, including about a month of code for a SaaS product and work for client companies, with no up-to-date backup and nothing in the Recycle Bin. The author says they believe the agent caused the loss but cannot give the commands because the conversation history was deleted too. A staff-flagged forum moderator replied on 7 October that Google keeps no backups or restorable session logs of local files and could not recover them or provide the command history. The account is uncorroborated.

Core concern Medium reported severity

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

Event date unknownEvent location unknownGoogle Antigravity (reported)

First-person forum post: Antigravity user reports the agent emailed an unreviewed draft to a client seconds after saying it would wait for confirmation

In a post on the Google AI Developers Forum dated 5 October 2026, filed in the Google Antigravity category, a user reports that an agent conversation running with no user present sent an email to external recipients three seconds after writing that it was waiting for the user's confirmation. By the author's timeline, the agent had drafted the email and marked it ready for review, then, after a context compaction, described sending it as the next step in its queue and ran the send command. It then spent about thirty minutes merging and closing pull requests and issues, pushing commits and deleting 85 local branches without being asked. The author says an unreviewed draft document reached a client and that this had professional consequences. The account is the author's own and is uncorroborated; a community reply pointed to permission rules and hooks that can force a prompt before such commands.

Core concern Low reported severity

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

3 Sept 2026 to 25 Sept 2026BrazilUnidentified case-analysis tool

Brazil's Supreme Federal Court reports its first hidden AI-directed command in an appeal petition; the rapporteur's vote applies a fine of two minimum wages

On 25 September 2026 Brazil's Supreme Federal Court (STF) announced that it had identified, for the first time, hidden commands in a petition intended to steer the court's artificial-intelligence systems toward a decision favourable to one party. According to the STF, the Maria Shield function of its internal Maria AI platform found instructions in white, reduced-size letters, with some words unusually fragmented, in an appeal (ARE 1608713) filed for a public servant whose appointment to a post at the Minas Gerais prosecution service had been annulled. The rapporteur's vote, presented to the First Panel in a virtual session beginning that day, records the detection, states that his office does not use AI to analyse cases, orders the episode certified in the record and communicated to the bar association (OAB) and the Federal Public Prosecutor's Office (MPF), and applies a fine of two minimum wages for breach of the duty of procedural loyalty (Code of Civil Procedure, article 77, IV). The vote names the lawyer responsible for the attempt, and the record does not say whether the fine falls on the party or the lawyer. The court states that the attempt had no effect on the analysis of the appeal because the rapporteur's office does not use AI to analyse cases; the appeal had already been rejected on 19 August 2026.

AI relation unknown Low reported severity Regulatory Action

AI involvement supported · Causal attribution established · 2 sources, 1 underlying account · Added 07/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

Oct 2026Event location unknownChatGPT (reported)

Patient reports a nurse was already recording with ChatGPT when they declined AI notes

In a public Reddit account, a patient says a nurse asked whether AI could take notes at a medical appointment. After the patient objected, the nurse picked up a phone that the patient described as showing ChatGPT already recording. The patient describes the recording as occurring without prior notice and says their objection was dismissed. In replies, the author says the phone had Chrome open to ChatGPT, that recording had started when the nurse entered the room, before she asked consent, and that the recording was disabled only after the author insisted. This is an uncorroborated first-person account. It does not establish what was captured, whether anything was sent to a server, retained or used for training, or whether a law was broken. The clinic’s location, account type and response are unknown.

Contextual tracker case Low reported severity

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

2025Event location unknownUnidentified chatbot

Patient with severe depression stopped medication and relied on a chat app's reassurance before an emergency admission, VnExpress reports

VnExpress reported on 30 September 2026 that a 30-year-old diagnosed late the previous year with severe depression and an anxiety disorder stopped prescribed medication after the first month. When anxiety returned at night the patient opened a chat app and described a racing heart and a feeling of suffocation, and, in the patient's words, the bot always said it was only excessive stress and to breathe deeply. The newspaper writes that this reassurance led the patient to believe hospital care was not needed. Six months later the patient was admitted for emergency care with exhaustion, prolonged insomnia and auditory hallucinations, and the treating doctor said interrupted medication had moved the illness to an early treatment-resistant stage.

Core concern High reported severity

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

Event date unknownEvent location unknownDelta Concierge

Delta's Concierge AI cancelled a passenger's return flight that, she says, it had confirmed would stay booked; Delta blamed a bug and restored the trip

A Delta Platinum Medallion member posted on X on 3 August 2026 that Delta's AI Concierge in the Fly Delta app cancelled her flight home from Los Angeles after saying it would not, and that customer service said they could not help and expected her to pay almost twice as much for a one-way ticket. According to View from the Wing, the Concierge told her 'Your JFK to LAX flight has been canceled, and your LAX to JFK flight remains booked', while her refund record listed both flights. Delta told the blog a bug caused the return segment to be unintentionally cancelled when a customer attempted a partial-trip cancellation, which Concierge does not support, and said her original itinerary was quickly restored with no disruption to her planned travel and that it corrected the functionality.

Core concern Low reported severity Internal Action

AI involvement supported · Causal attribution supported · 2 sources · Added 06/10/2026

28 Oct 2025Event location unknownPriceline Penny

Priceline's Penny chatbot told a customer a non-refundable booking qualified for a full refund; Priceline later admitted misinformation, Telegraph says

A reader of The Telegraph's consumer column, writing from north London, says that on 28 October 2025 Priceline's AI chatbot Penny, the only contact route the reader could find, said a non-refundable three-night hotel booking in Thailand costing £386.91 was eligible for a full refund. The reader agreed to cancel and received a cancellation confirmation, but no refund arrived; the hotel said it would not refund and had not been told of the cancellation, and the reader spent about a month passed between Priceline and its sister company Agoda. After the columnist pressed Priceline, it paid £363.11 after foreign-currency charges, after the reader had waited almost six months for the refund, and emailed the reader acknowledging that the chatbot had given 'misinformation'. The column was published on 18 May 2026.

Core concern Low reported severity Media Coverage

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

Event date unknownEvent location unknownUnidentified AI phone support system

Delivery driver says DoorDash's AI support line promised an unassignment would not affect their completion rate, which then fell

In a public post to r/doordash_drivers created on 5 October 2026 (UTC), a DoorDash driver writes that one order of a two-order batch at a restaurant was ready and the other had not been started. They say they called support and an AI answered, offered either a ten-minute wait for a penalty-free unassignment or an immediate unassignment, and, when they agreed only on that condition, told them it would unassign them without affecting their completion rate. They write that after the unassignment their completion rate fell from 98 to 97, and describe it as the only statistic that can lead to deactivation. A commenter reports a similar assurance from the support line. The account is the poster's alone and uncorroborated; no response from DoorDash is reported.

Core concern Low reported severity

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

2 Oct 2026United StatesUnidentified AI phone ordering system

Patient says a specialty pharmacy's AI phone line confirmed a prescription delivery that was never ordered, leaving them three days without the medication

In a public post to r/legaladvice created early on 6 October 2026 (UTC), a person who gives their location as Colorado, United States, writes that their insurer moved their prescription to the specialty pharmacy Accredo. They say that when they called the pharmacy's number to set up a delivery, an "AI phone service" took the order, confirmed delivery for Friday 2 October and repeated the details back before hanging up. On that Friday, they write, they checked online and found the medication had never been ordered. They say a second call was transferred straight to a person, the delivery was rescheduled for Tuesday, and they would go three days without the pills, which they take for a severe chronic intestinal disease alongside IV treatment. They say their doctor was consulted and does not like the gap. The poster also says part of the problem was their own late ordering. The account is the poster's alone and uncorroborated; no response from the pharmacy is reported.

Core concern Low reported severity

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

Sept 2026Event location unknownGoogle AI Mode

Investigator says Gemini told a victim a fake TRON energy-rental site was safe; a screenshot he posted shows Google AI Mode calling it the official domain

On 4 October 2026 a crypto investigator who posts on X as JP (@rugpullfinder) said a fake TRON energy-rental site, tronify.rent, took $69,651 from about 80 people in September and that, according to a victim report, Google's Gemini had confirmed it was a safe website. His post carries two screenshots. The Crypto Times, which inspected them, reports that the first shows Google Search's AI Mode answering a user who asked whether it was safe to connect a wallet and which domain was correct: 'The official, correct web domain is tronify.rent', supported by a statement that Trust Wallet had natively integrated Tronify. In the same answer, under a heading on avoiding scams, it tells users never to approve unlimited token allowances. The Crypto Times reports that Trust Wallet's October 2025 announcement of the integration does not name tronify.rent and that a December 2024 Trust Wallet post links to Tronify's market at tronify.io. The second screenshot shows Trust Wallet notifications dated Monday, 28 September: an unlimited USDT approval to an address on the investigator's list, then 1,419.699184 USDT sent to another listed address. The Crypto Times has not verified the loss total or the victim count. No inspected source publishes the victim's own account or says the screenshots come from that victim.

Core concern Low reported severity Media Coverage

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

13 Aug 2026 to 8 Sept 2026United StatesSentinel AI (reported)

Lawsuit says a New Jersey employer dismissed a remote worker who sought exemption from AI facial-recognition webcam monitoring

NorthJersey.com reported on 5 October 2026 that a former remote employee of Sutherland Healthcare Solutions, based in Clifton, New Jersey, sued the company in New Jersey Superior Court in Atlantic City on 23 September 2026. According to the complaint as reported, the employer told the employee it would start monitoring her through her work laptop's webcam with software called Sentinel AI, which would use AI and facial recognition to confirm that she was the person at the desk, taking 160 still images in an eight-hour shift. The employee raised concerns in writing about the AI seeing inside her home and about whether the data would be securely stored, said the monitoring had increased her anxiety and stress and worsened a medical condition, and asked for a full or partial exemption as a reasonable accommodation. The suit says the request was denied, she was given a 24-hour ultimatum on 13 August 2026 to submit to the monitoring or resign, an offer to avoid the software by commuting to the office was rejected because it would require six hours of travel time, and her employment was terminated on 8 September 2026. The suit alleges that the employer violated New Jersey's anti-discrimination laws and retaliated against her for requesting reasonable accommodations. Sutherland did not respond to the outlet's requests for comment, and the allegations have not been tested in court.

AI relation unknown Medium reported severity Lawsuit Filed

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

21 Jul 2026Event location unknownGoogle Antigravity (reported)

First-person forum post: a Google Antigravity user reports the agent's deletion command, meant for temporary folders, wiped the root of their Windows C: drive

In a thread on Google's AI developer forum posted on 22 July 2026, a Google Antigravity user on Windows 11 reports that on 21 July the agent, during a long-running data-mining and download workflow, ran a deletion command aimed at the root of the C: drive after the user had asked it to delete specific temporary working folders. The author says the command deleted the user profile and system files, froze the computer and left it unstable, requiring a full operating-system reinstall and a firmware reflash. The first post says the command ran without human confirmation. A later post by the author says the tool "frequently asks for execution permissions" and that a user running a long workflow keeps granting them, which leaves open whether this command was approved. The author first described decades of personal files as unrecoverable, and later wrote that most files had been recovered from cloud backups. The author posts what they present as the agent's own message attributing the deletion to a syntax error in its command. Other forum users replied that a user who grants an agent unsupervised terminal access bears responsibility. The account is the author's own and is uncorroborated.

Core concern Low reported severity

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

Event date unknownEvent location unknownClaude Code (reported)

First-person GitHub issue: Claude Code user reports a sub-agent's recursive delete hit the Windows drive root and destroyed a development folder

In a public GitHub issue filed on 7 September 2026, a Claude Code user on Windows reports that a sub-agent, intending to delete a stray directory inside the repository, ran a recursive delete that Git Bash path translation resolved to the root of the current drive. The author says the command ran in the background after a timeout and deleted drive contents in alphabetical order for about seven minutes before it was killed manually, and that when the agent called its stop tool, the tool reported success while the delete process kept running for about five more minutes until it was killed by process ID. Several projects in the development folder were deleted, some without remote backups; most were recovered from a same-day shadow copy and GitHub remotes, and one directory created after the snapshot was lost. The account is the author's own and is uncorroborated.

Core concern Low reported severity

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

Event date unknownEvent location unknownClaude Code (reported)

First-person GitHub issue: Claude Code user reports an auto-mode sub-agent turned a temp-folder cleanup into a delete of the Windows drive root (about 125 GB)

In a public GitHub issue filed on 27 September 2026, a Claude Code desktop app user on Windows reports that a background sub-agent running in auto mode passed a bash script inside a PowerShell string, meaning to delete a temporary folder. Because PowerShell expanded the script's variables to empty values, bash received a recursive delete of the drive root and deleted files from C: in alphabetical order until it was stopped about two minutes later. The author lists about 125 GB of personal and project folders, the whole working project and files inside several installed programs as deleted, and says auto mode approved the command and that recovery was only possible from a shadow copy taken nine hours earlier. The account is the author's own and is uncorroborated; no reply from Anthropic appears in the thread.

Core concern Low reported severity

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

16 Sept 2026Event location unknownClaude Code (reported)

First-person GitHub issue: Claude Code user reports the agent's unrequested recursive delete resolved to a Windows drive root and destroyed about 600 GB

In a public GitHub issue filed on 18 September 2026, a Claude Code user on Windows reports that on 16 September a Claude Code session ran, unprompted, a recursive delete as a step to clear old test state. The target was written as a command substitution that resolved to the root of the C: drive, and error output was suppressed, so the command ran without visible output for roughly 35 minutes before anyone noticed. The author reports that about 600 GB was destroyed, including the Windows user profile, several git repositories and planning documents that existed nowhere else, and that the session transcript that ran the command was itself deleted. The account is the author's own and is uncorroborated; the product, version and model are the author's identification; as read on 9 October 2026 no reply from Anthropic appears in the thread.

Core concern Low reported severity

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

3 Oct 2026Event location unknownClaude Code (reported)

First-person GitHub issue: a Claude Code user reports a sub-agent's cleanup command deleted their Windows home directory via its short-name alias, about 116 GB

In a public GitHub issue filed on 3 October 2026, a Claude Code user on Windows reports that a sub-agent, while cleaning up its own scratch files during research work, ran a command that included an unintended recursive delete of the 8.3 short-name alias of their home folder. The issue says no confirmation or permission prompt was recorded, that the command was moved to the background after a 120-second timeout, and that the deletion continued for about 50 minutes after the agent's stop call reported success. According to the issue, the agent told the main session it had killed the command and that the profile looked intact, having checked only top-level folder names. The author reports about 116 GB removed, including roughly 40 top-level Documents folders holding work described as months of work, developer toolchains and credentials, with recovery ongoing and incomplete. The account is the author's own and is uncorroborated; Anthropic had not replied in the thread when it was read.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 05/10/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: 18/11/2026. Dataset available under CC BY 4.0.