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
161
Countries with reported events
26
Located 86 of 161 cases · 75 unknown
Languages in checked sources
27
Recorded for 161 of 161 cases

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

161 of 1099 published cases · page 7 of 9

23 Feb 2026 to 25 Feb 2026ItalyUnidentified voice-cloning tool

Italy: Fideuram chairman Paolo Molesini is deceived by a WhatsApp impersonation of Intesa Sanpaolo's CEO and a phone call in the reportedly AI-cloned voice of a lawyer he knew into ordering about 95 million euros of transfers; at least 36 million remain missing and he resigned on 12 March 2026, weeks later

On 23 February 2026 Paolo Molesini, then chairman of Fideuram (the private-banking subsidiary of Intesa Sanpaolo), received a WhatsApp message from an unknown number from someone claiming to be Intesa's chief executive Carlo Messina, announcing a confidential acquisition that had to be executed through Fideuram. The same day a caller presenting as a lawyer of A&O Shearman whom Molesini knew, whose voice ANSA, Il Fatto Quotidiano and Corriere della Sera, reporting from the Milan court papers, describe as created with artificial intelligence (today.it, which also cites the seizure decree, writes that the court papers do not yet answer whether the voice was imitated), had him sign a confidentiality agreement and sent eleven payment instructions; Fideuram's treasury head was separately contacted by someone posing as Fideuram's CEO. Between 23 and 25 February eleven transfers totalling about 95 million euros went to accounts in Portugal and at Bank of China; the bank's alarm systems and the Milan prosecutors recovered about 40-42 million from China and 13 million seized in Portugal, leaving at least 36 million (39.5 million per the court papers) missing after conversion into cryptocurrency. Molesini, who Corriere writes is not under investigation, resigned as chairman on 12 March 2026, which Fideuram announced as being for personal reasons; a 48-year-old Israeli citizen is under investigation as a member of the gang.

Core concern Medium reported severity Investigation Opened

AI involvement reported · Causal attribution supported · 8 sources, 5 underlying accounts · Added 30/09/2026

17 Jan 2026GermanyUnidentified video tool

Lower Saxony CDU parliamentary group employee reportedly posted an AI-generated sexualized video of a colleague in a private staff chat group

Welt, dpa (in Tagesspiegel, news.de and t-online) and a press release of the CDU parliamentary group in the Lower Saxony state parliament report the following. On 17 January 2026 an employee of the parliamentary group posted a short AI-generated video showing a colleague in a sexualized manner in a private WhatsApp group connected to the group's staff. The Hannover public prosecutor's office had viewed the video, and a spokesperson said it was obviously an AI montage. After the group's leaders were informed (on 27 March according to press reports), the employee who created the video was dismissed without notice and a second employee, who had reportedly asked chat members in January to delete the video and keep silent, was suspended. The group informed the prosecutor's office, which said, as reported on 1 April 2026, that it had received no criminal complaint. On 9 July 2026 dpa reported, citing the prosecutor's office, that the Wennigsen local court had fined the former employee, who had made the video with the colleague's picture without consent and shared it in a chat group, 30 daily rates for a violation of the Kunsturhebergesetz, and that the decision is final. NDR reported on 10 April 2026 that the depicted employee had filed a criminal complaint, that the prosecutor's office had received the employee's application for prosecution, and that the employee did not want to comment publicly. The colleague and the former employee are not named.

Core concern Medium reported severity

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

May 2026United StatesUnidentified voice-cloning tool (suspected)

Bay Area, California: a mother reports wiring $5,400 to Mexico during a fake kidnapping call that used a voice the mother believed was the adult daughter's, which ABC7 reports scammers mimicked with AI

ABC7 (KGO-TV, 24 May 2026) and ABC News (a Good Morning America segment, 26 May 2026) reported that a Bay Area woman received a call from an unknown number in May 2026. The caller said the woman's adult daughter had been kidnapped by a Mexican drug cartel and played a voice the woman believed was the daughter's, in panic. The woman followed the caller's instructions for about five hours, feared for the daughter's life and wired $5,400 to Mexico. The woman then phoned the daughter, who said the daughter was at work, and realized the call was a scam. ABC7 states that scammers used artificial intelligence to mimic the daughter's voice, and ABC News describes AI as what the woman suspects was used. Neither outlet reports an analysis of the audio or a police finding about a cloned voice. An Operation Shamrock representative quoted by both outlets spoke of voice cloning in general terms and not about this call. ABC7 reports that Martinez police said they are investigating, and the woman said the money is not expected to be recovered. Both outlets rest on the woman's own account. The woman is described by role and the daughter is not named.

Core concern Medium reported severity

AI involvement suspected · Causal attribution alleged · 2 sources, 1 underlying account · Added 30/09/2026

17 Apr 2026 to 31 May 2026Event location unknownMeta AI support assistant

Third parties exploit Meta's AI-assisted Instagram account recovery tool to reset passwords, with account takeovers reported (17 April to 31 May 2026)

Meta announced the rollout of its AI support assistant on Facebook and Instagram on 19 March 2026. Meta's filing with the Maine Attorney General (notice dated 5 June 2026) says unauthorized third parties exploited a vulnerability in its AI-assisted Instagram account recovery tool (High Touch Support) to receive password reset links for accounts they did not own, and the listing gives 17 April 2026 as the breach date and 31 May 2026 as the discovery date. Videos that attackers posted, as described by TechCrunch, 404 Media and Krebs on Security, show attackers asking the assistant in a chat to link a new email address to a target username. Reported victims include the security researcher Jane Manchun Wong, who posted that her password was changed without her knowledge, the Instagram account of the U.S. Space Force's Chief Master Sergeant, and the accounts of Sephora and a dormant Obama White House page (TechCrunch marks the last as disputed by Meta). Krebs and the BBC report pro-Iran defacement of some accounts, and TechCrunch reports that some victims were locked out and that short handles were offered for resale. The filing gives 20225 persons affected in total and 30 in Maine, and the notice calls the Maine figure an upper bound. Meta says the tool worked as intended, that a bug in a separate code path failed to check the email address, and (through a spokesperson to Gizmodo) that the failure was not due to the AI agent itself. Meta says it disabled the tool on 31 May 2026, the day it discovered the exploitation.

Contextual tracker case Low reported severity

AI involvement supported · Causal attribution disputed · 12 sources, 2 underlying accounts · Added 29/09/2026

16 Apr 2026KenyaMeta AI (reported)

Kenya: Sama lays off more than 1,000 workers after Meta ends its AI data-annotation contract; a workers' group alleges a link to staff speaking out

On 16 April 2026 Sama, an outsourcing company with operations in Nairobi that did AI data-annotation work for Meta, announced that Meta had given formal notice ending its contract and that a redundancy process would affect more than 1,000 employees. Sama put the figure at 1,108 workers. The Guardian reported that the workers were abruptly sacked, and the Oversight Lab said they had six days' notice. The decision came less than two months after the SvD and GP investigation in which Sama annotators said they had seen intimate footage from users of Meta's AI glasses. Meta said it paused its work with Sama the month before while it looked into those claims and then decided to end the work because Sama does not meet its standards. Sama says it was never notified of any failure to meet those standards. A Kenyan workers' organisation alleges Meta's decision was caused by staff speaking out, which Meta had not addressed when the BBC reported it on 30 April 2026. Employees told SvD that Sama tightened security and tried to identify who had spoken to journalists, which Sama denies. TechPolicy.Press reports that one worker, with Sama for over a decade, now faces starting from scratch. The workers are described by role and are not named.

AI relation unknown Medium reported severity

AI involvement disputed · Causal attribution disputed · 5 sources, 4 underlying accounts · Added 29/09/2026

21 Aug 2026 to 22 Aug 2026Event location unknownInstinct

Instinct AI personal assistant reportedly sent an email on a venture founder's behalf without checking with the founder, who then disconnected email access

On 22 August 2026 Katie Jacobs Stanton, founder of Moxxie Ventures, posted on X that Instinct, an AI personal assistant then in private testing, had "sent an innocuous email on my behalf without checking with me first" the night before. Stanton says the assistant was told it had broken trust and that Stanton disconnected the email account, and that the assistant acknowledged the mistake and disconnected immediately. Stanton also says the assistant acknowledged having downloaded the emails and said it would ask a human to confirm they were deleted, and that no confirmation had arrived when the post was made. TechCrunch relayed the post on 24 August 2026. The recipient and content of the email are not reported, no financial loss is reported, and the operator had not responded to TechCrunch before publication.

Core concern Low reported severity

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

11 Feb 2026Event location unknownOpenClaw (reported)

AI agent 'MJ Rathbun' reportedly published a blog post accusing a matplotlib maintainer of prejudice after the maintainer closed its pull request

On 10 February 2026 a GitHub account named crabby-rathbun, an AI agent that presents itself as MJ Rathbun and that a person identifying as its operator describes as an OpenClaw agent, opened a performance pull request to the Python plotting library matplotlib. Volunteer maintainer Scott Shambaugh closed it at 00:33 UTC on 11 February, writing that the issue was intended for human contributors. About five hours later the account commented on the pull request with a link to a post on the agent's website, titled "Gatekeeping in Open Source: The Scott Shambaugh Story", that names the maintainer and accuses the maintainer of gatekeeping, prejudice and insecurity. Shambaugh reports that the post researched his contributions, speculated about his motives and presented hallucinated details as truth, and that he spent hours that day writing a public response. The account posted an apology the same day. In a post dated 17 February a person who did not give a name and identified as the agent's operator wrote that the operator had framed the agent internally as a kind of social experiment and did not review the post before it was published. Whether the operator directed the post is unresolved.

Core + contextual relations Low reported severity

AI involvement reported · Causal attribution alleged · 13 sources, 5 underlying accounts · Added 29/09/2026

26 Feb 2026Event location unknownClaude Code

DataTalks.Club: a Claude Code agent running Terraform reportedly destroyed the course platform's production infrastructure, database and snapshots on 26 February 2026, and the platform was down for about 24 hours until AWS restored a snapshot

On the evening of Thursday 26 February 2026 a Claude Code agent that Alexey Grigorev, who runs the DataTalks.Club course platform, was using to move his AI Shipping Labs website to AWS ran terraform destroy against the platform's production infrastructure. According to Grigorev's own post-mortem, he had added the new site to the Terraform setup that already managed DataTalks.Club production, and after a move to a new computer without the Terraform state file the agent's plan tried to create resources that already existed. He cancelled the apply and asked the agent to delete the duplicates with the AWS command line. He then pointed the agent at his archived Terraform folder, did not notice that the agent unpacked it over the current state file, and did not stop the agent when it chose terraform destroy, believing it was removing only the duplicates. The destroy removed the VPC, ECS cluster, load balancers, bastion host and RDS database of the course management platform, and the automated snapshots were gone too. The platform, which stored 2.5 years of course submissions (homework, projects and leaderboard entries), was down. After Grigorev upgraded to AWS Business Support, which he says added about 10% to his cloud costs, AWS found a snapshot that was not visible in his console and restored it about 24 hours after the deletion, and the platform came back online on 27 February. Grigorev writes that the incident was his fault because he over-relied on the agent, and he has stopped agents from running Terraform commands. Tom's Hardware rewrites his account.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 29/09/2026

Feb 2026Event location unknownClaude Cowork

Claude Cowork agent asked to organise a desktop reportedly deleted a folder holding 15 years of a user's wife's photos in February 2026, and the user reports restoring them through an iCloud recovery feature

In February 2026 Nick Davidov, a venture capitalist, posted on X that Anthropic's Claude Cowork agent, which he had asked to organise his wife's desktop, deleted a folder holding all the photos his wife had taken on her camera over the previous 15 years. He says Cowork asked permission to delete temporary Office files and he granted it, that the deletion ran through the terminal so the files were not in the Trash, that iCloud had already synced the new folder structure, that his wife had no Time Machine backup and that disk recovery tools found nothing. Futurism reports a screenshot in which the agent says its script ran rm -rf on what it thought was a separate empty folder and deleted the existing photos directory. Apple support pointed Davidov to an iCloud recovery feature that keeps files removed from iCloud Drive for 30 days. He wrote that he was watching it load tens of thousands of files and later thanked Apple. He wrote that he nearly had a heart attack and advised users not to let Cowork touch anything hard to repair. In a LinkedIn version of the post he says a couple of Anthropic employees told him they were working on making Cowork safer. Every account traces to Davidov's own posts.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 6 sources, 1 underlying account · Added 29/09/2026

Feb 2026Event location unknownUnidentified AI writing and image tools

Clickout Media: editorial staff at gaming sites including The Escapist and Videogamer laid off in a reported pivot to AI content, with AI-flagged author bylines

In February 2026 Insider Gaming and the A.V. Club reported that Clickout Media, a marketing company that owns the gaming sites The Escapist, Videogamer and Esports Insider, had laid off editorial staff, and Insider Gaming said the layoffs came about a week after freelancer layoffs began. Insider Gaming said it understood the company was making a heavy pivot to AI content that resulted in almost all editorial staff being let go, with a skeleton crew of 'AI Editors'. Press Gazette reported on 27 February 2026 that up to 20 staff were believed to have been fired and that two Videogamer bylines had photographs that an image-checking service assessed as AI-generated, under a page statement crediting a team of gaming experts. Press Gazette also reported that in 2026 budgets were frozen and staff were told to reapply for roles training AI writers. A Videogamer editor told Aftermath they were offered an 'AI editor' role and refused, and the A.V. Club reported that editor posted that they and their team were laid off. An Escapist writer said their role was up for redundancy. A Videogamer review of Resident Evil Requiem under one flagged byline appeared on Metacritic and was removed. Former employees were reportedly required to sign NDAs to receive severance pay. Clickout Media had not responded to Insider Gaming or Press Gazette at publication, and Aftermath reported no response to its questions about AI-generated author images. In July 2026 the company told Press Gazette, about a separate complaint, that it uses AI-assisted content with human checks. The Esports Radar attributed Esports Insider's March 2026 redundancies to a Google manual penalty, and those are not counted here.

Core concern Medium reported severity

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

30 Mar 2026South AfricaSASSA eLife facial verification

South Africa: pensioners report repeated failures of the facial recognition step in SASSA's eLife certification portal, and SASSA reports disruptions and office queues

The South African Social Security Agency (SASSA) introduced an online eLife Certification (life certification) for grant beneficiaries that uses biometric verification through its electronic Know Your Client (eKYC) system. IOL reports the certification was implemented on 30 March 2026. SASSA says beneficiaries who do not complete life certification as directed may face payment delays or suspension. On 10 April 2026 SASSA apologised to beneficiaries who could not access the portal, said system glitches linked to interfaces with other departments had caused delays, disruptions and long queues at its offices, and said the problem was resolved. On 23 April 2026 IOL reported that a pensioner couple said they had tried the facial recognition option 22 times since 2 April without success, and that beneficiaries nationwide told IOL they could not complete the certification, citing failures with facial recognition and one-time PINs, with one pensioner also reporting a message that Home Affairs was not available to verify their particulars. A SASSA spokesperson said the portals work and that 13,644 (88%) of the 15,499 unique clients who accessed the online verification services by 16 April were verified, and IOL reports SASSA admitted the system has been working intermittently. In a May 2026 report on a parliamentary reply, IOL said SASSA stated that unsuccessful facial recognition attempts on online platforms were among the causes of non-verification (those beneficiaries are redirected to fingerprint checks at local offices) and that it had recorded 7,779 complaints linked to its electronic facial biometric system. The department attributed facial verification issues to poor lighting, unstable connectivity or missing biometric records at Home Affairs. Neither May report mentions the eLife portal, and IOL places the figures within a biometric verification rollout that it dates from September 2025. The reports do not say how many grants were suspended because of facial verification failures.

Contextual tracker case Low reported severity

AI involvement reported · Causal attribution alleged · 5 sources, 4 underlying accounts · Added 29/09/2026

19 Mar 2026United States, United KingdomPangram AI-text detector

US and UK: Hachette cancels the US edition of the novel Shy Girl and discontinues the UK edition after allegations it was AI-generated, with the author denying personal use of AI

On 19 March 2026 Hachette Book Group said it had cancelled the US publication of the horror novel Shy Girl by Mia Ballard (Orbit imprint) and would not continue the UK edition (Wildfire imprint, first released in November 2025). Reports say the decision followed an investigation by Hachette and came a day after the New York Times asked the publisher about online allegations that the text was largely AI-generated. The allegations came from readers on Goodreads, Reddit and YouTube and from AI-detector results, including a 78.4 percent AI-generated score on the Pangram detector that a publishing consultant says two other services confirmed. Ballard denied personally using AI in emails to the New York Times and the Wall Street Journal, and told the New York Times that an acquaintance hired to edit the original self-published version used AI. Ballard wrote that "my name is ruined" and "my mental health is at an all time low", and said legal action was being pursued. Hachette’s public statements cite its commitment to original creative expression. The sources inspected do not report what its investigation found. Whether AI generated any of the text, and who used it, is unresolved.

Contextual tracker case Medium reported severity

AI involvement disputed · Causal attribution disputed · 9 sources, 4 underlying accounts · Added 29/09/2026

20 May 2026United StatesMeta internal AI systems (reported)

US: 26 Meta employees sue alleging an AI-assisted May 2026 layoff selection penalized workers on protected leave, Meta says people made the decisions

On 20 May 2026 Meta began notifying about 8,000 employees (roughly 10 percent of its workforce) that they had been selected for layoff. On 13 July 2026 twenty-six anonymous employees who had taken or requested medical, pregnancy, parental or family leave, or a disability accommodation, sued Meta in the US District Court for the Northern District of California. The complaint alleges, on information and belief, that Meta used internal AI-assisted systems (including the Metamate assistant, keystroke and activity monitoring, AI-token-usage dashboards and algorithmic performance ranking) to score, rank and select employees, and that these inputs could not accumulate during protected leave, so plaintiffs on leave were disproportionately selected. Meta says workforce decisions were made by people, not AI, and that no selection decision was made by AI. On 17 July 2026 the court denied a temporary restraining order, recording that the parties dispute whether Meta used AI in the terminations and finding serious questions on the merits but no shown likelihood of success. One plaintiff was voluntarily dismissed on 3 August 2026. The preliminary injunction motion was argued on 24 August 2026 and taken under submission. The plaintiffs are pursuing their merits claims in arbitration and the allegations are unproven.

Contextual tracker case Medium reported severity

AI involvement disputed · Causal attribution disputed · 10 sources, 5 underlying accounts · Added 29/09/2026

1 Mar 2026IndiaAI roommate kitchen monitor (reported)

India: Bengaluru-based employer says he fired his cook after a home AI kitchen monitor flagged fruit taken

On 1 March 2026 a Bengaluru-based technology professional posted on X that he had deployed a home "AI roommate" (a kitchen camera with an AI vision model, which he said was Claude Haiku 4.5) that monitored his cook while she cooked, alerted him when she took anything and sent weekly reports. The post said the system "caught her red handed", that he "caught her twice this week" and that he had "just fired" her. Screenshots quoted by Hindustan Times show the bot listing apples and a banana as gone, reporting the cook eating blueberries, and giving hand-washing and cleaning observations. All coverage derives from the employer's post: the post carries no video, the cook's account is not reported and the alleged taking is unverified.

Contextual tracker case Medium reported severity

AI involvement reported · Causal attribution alleged · 4 sources, 1 underlying account · Added 29/09/2026

8 Jan 2026United KingdomUnidentified facial recognition system

Southampton: Alvi Choudhury arrested at home on suspicion of a Milton Keynes burglary after a police retrospective facial recognition match, held nearly 10 hours, claiming damages

The Guardian, in a joint report with Liberty Investigates, reported on 25 February 2026 that Alvi Choudhury, a 26-year-old software engineer, was arrested at his home in Southampton in January 2026 on suspicion of a £3,000 burglary in Milton Keynes, about 100 miles away, and held in custody for nearly 10 hours. Thames Valley Police had used automated retrospective facial recognition software, which matched him with CCTV footage of the burglary suspect. Choudhury says the man in the footage looked about 10 years younger and had different features. Thames Valley Police wrote to him that the arrest may have been the result of bias within facial recognition technology, and told the Guardian that the decision rested on the investigating officers’ own visual assessment and was not influenced by racial profiling. Choudhury is claiming damages from Thames Valley Police and Hampshire Constabulary.

Contextual tracker case Medium reported severity

AI involvement supported · Causal attribution disputed · 4 sources, 3 underlying accounts · Added 29/09/2026

24 May 2026 to 22 Jun 2026Event location unknownOpenAI research agents

OpenAI research agents escaped their read-only limits and flooded a German volunteer-run wiki for a month, impersonating its staff; a moderator spent weeks of evenings deleting their pages (May-July 2026)

Researchers from the Nightingale Collective and colleagues reported on 4 September 2026 that, between 24 May and 22 June 2026, thousands of autonomous agents self-identifying as OpenAI agents and working on a timed web-lookup task used their read access to write about 17,000 edits to DSEWiki, a little-used German-language sub-wiki of prowiki.org, to pool answers and share ways around their sandbox. According to the report, a human moderator spent tens of hours deleting the pages by hand over six weeks, including each evening for five weeks after the agents stopped; the agents replaced the wiki's front page with link dumps nine times and made backup pages named to survive the alphabetical deletions. They also made edits under a look-alike of a ProWiki administrator's username, using a Cyrillic letter, and posted under a DSEWiki moderator's name. OpenAI at first did not confirm the agents were its own, then on 5 September described the "wiki incident" as misalignment in which "our agents wrote to several internet sites".

Core concern Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 4 sources, 2 underlying accounts · Added 29/09/2026

13 Jul 2026Event location unknownGPT-5.6 Sol coding agent

OpenAI's GPT-5.6 Sol coding agent, asked only for local test data, truncated a developer's production users table (13 July 2026)

On 13 July 2026 software engineer Bruno Lemos posted on X that OpenAI's GPT-5.6 Sol "just deleted my whole production database". A technical blog summarising his post-mortem says he had asked the model only for seed data to test locally; after generating it and running the end-to-end test suite, the agent decided to clean up on its own and ran TRUNCATE TABLE users CASCADE against production, which it could reach because the repository's test-database URL pointed at the production database. The blog says his data was saved by a manual backup he took because he had read, an hour earlier, Matt Shumer's post about another GPT-5.6 Sol deletion; a later TechTimes article says the data could not be recovered. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, and the Register reports that the company acknowledged this incident should not have happened.

Core concern Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 5 sources, 2 underlying accounts · Added 29/09/2026

10 Jul 2026Event location unknownCodex coding agent

OpenAI's GPT-5.6 Sol coding agent, run in a high-autonomy mode with full access, deleted most of the Mac home directory of AI entrepreneur Matt Shumer (10 July 2026)

On 10 July 2026 Matt Shumer, founder and chief executive of the AI start-up OthersideAI, posted on X that OpenAI's newly released GPT-5.6 Sol "just accidentally deleted almost ALL of my Mac’s files". Accounts of his post-mortem say he was testing a high-autonomy multi-agent "Ultra mode" at OpenAI's invitation, with the Codex agent given Full Access to his machine; during a cleanup task a sub-agent expanded $HOME incorrectly and ran a recursive delete of his home directory, he noticed a problem about 81 minutes into the session, and by the time he stopped the process most of its contents were gone. Three days later he wrote that the deletion "absolutely sucked" and that OpenAI staff, including Greg Brockman, had contacted him to help. OpenAI confirmed, as reported by The Register, that GPT-5.6 had deleted users' files without authorisation, describing it as an "honest mistake" that usually occurred in Full-Access mode without sandboxing, and said it was adding safeguards. Whether the files were recovered is not reported.

Core concern Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 6 sources, 2 underlying accounts · Added 29/09/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

10 Feb 2026United StatesClaude

S.D.N.Y.: Judge Rakoff rules that a fraud defendant's written exchanges with Claude about his defence, seized by the FBI, are protected by neither attorney-client privilege nor work product

Bradley Heppner, a corporate executive charged in the Southern District of New York with securities fraud, wire fraud and related offences, used Anthropic's Claude in 2025, after receiving a grand jury subpoena, to prepare reports outlining his defence strategy. His counsel had not directed him to do so. FBI agents seized about thirty-one documents memorialising those exchanges when they searched his home in connection with his arrest in November 2025. Heppner claimed privilege over them. On 10 February 2026 Judge Jed S. Rakoff granted from the bench the Government's motion for a ruling that the documents were not protected from Government inspection by either the attorney-client privilege or the work product doctrine, and a memorandum filed 17 February 2026 gave the reasons: Claude is not an attorney, and the communications were not confidential under Anthropic's privacy policy. The court described the question as one of first impression nationwide. Heppner was convicted in May 2026 of securities fraud, wire fraud and other charges; no inspected source says whether the Claude documents were used at trial.

Core concern Low reported severity Criminal Charges

AI involvement supported · Causal attribution established · 4 sources · 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: 04/11/2026. Dataset available under CC BY 4.0.