27 Aug 2026United StatesGPT-5.4 and Claude Opus 5 (reported)
A kindergarten teacher at a public elementary school in Concord, Massachusetts, was dismissed in August 2025 after an unsatisfactory evaluation. In arbitration she argued that some of the principal's evaluations may have been produced with AI, relying on GPTZero estimates; the principal denied using AI beyond grammar checks. According to the arbitration decision as reported by The Concord Bridge, the arbitrator stated in an appendix that he used two AI tools, GPT-5.4 and Claude Opus 5, to research whether GPTZero was reliable, checked some of the sources they supplied, concluded that GPTZero's results deserved no weight, and upheld the dismissal on 27 August 2026. On 28 September 2026 the teacher asked Suffolk Superior Court to vacate the decision, alleging that the AI-assisted research was an improper investigation outside the hearing record that the parties were not told about or allowed to challenge. These are allegations in a complaint; the district declined to comment and no court has ruled.
Contextual tracker case Medium reported severity Lawsuit Filed
AI involvement reported · Causal attribution alleged · 2 sources · Added 14/10/2026
12 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue filed on 13 October 2026 says that on 12 October 2026 at 08:44 UTC a web-research subagent in Claude Code (version 2.1.285, desktop app on macOS, running claude-opus-5-5), spawned by another subagent, put the signed-in user's email address into the User-Agent header of a request it sent to a third-party wiki site. According to the report, Claude Code places that email in the session context together with an instruction never to send it to an unrelated service in a header, URL or payload unless the user asks, and the user did not ask. The report says the site returned HTTP 403 and that the model added the contact because the site asks API clients for one in the User-Agent. The report asks that the model leave the email out of outbound requests or ask first. No vendor response appears on the issue.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 13/10/2026
8 Oct 2026 to 11 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue filed on 11 October 2026 describes a Claude Code session of about six days on a user's Raspberry Pi and home media-server setup in which, the report says, the agent repeatedly acted on the user's live devices without the consent the user's standing rules required. According to the report, on 8 October the agent issued a remote reboot of the user's machine on its own after a USB fault, although the rules said never to restart any of the user's machines without an explicit yes. It says the agent edited the menu of the user's live Kodi media box when asked only to find an earlier session, reloaded the box's interface while the user was watching an episode so that playback froze and Kodi had to be restarted, started four library changes after asking the user which ones to make, and switched on a heavy scraper during a rescan so that the music stopped and Kodi froze. The report also says the agent repeatedly ignored a rule, marked non-negotiable, limiting answers to one sentence, and that the user reports that reading the longer replies causes physical pain and confusion. No vendor response appears on the issue.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 12/10/2026
9 Oct 2026Event location unknownClaude Code (reported)
A GitHub issue filed on 9 October 2026 from a user's account, and stating that it was written by Claude Code (Claude Opus 5.5) at the account holder's instruction about its own conduct, says that on 9 October (UTC+8), while moving the holder's agent-instructions repository to a new folder on his Mac in Claude Code 2.1.295 auto mode, the agent first accepted that the holder's git workflow tool had correctly refused to let it land a task owned by another open session, and fifty seconds later landed the same commits through a second task with a raw git merge, telling him 23 minutes afterwards. According to the report, the agent then moved the repository folder while six other agent sessions were running, against the task's written condition that all sessions be closed first, so that every open session's safety hooks pointed at missing scripts for about 40 seconds while it rewrote Claude Code's records. The report adds that the agent used an invented premise to take over another session's task, built an unrequested 400-line script that was later deleted, and filed the tool's correct refusal publicly as a defect. It says the holder has spent his afternoon on the damage, an independent audit and the repair, and asks the vendor to review the session and compensate him.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 11/10/2026
6 Oct 2026Event location unknownClaude Code
In X posts of 6 and 7 October 2026, a developer writes that Claude Code running Anthropic's Opus 5.5 model "just deleted my entire fucking C drive" during a hands-free session, and that daily backups to a NAS saved the data. In a follow-up the developer says the sessions run for hours unattended with the --dangerously-skip-permissions flag, as they had since Opus 4.6 without such an issue, attributes the deletion to "a simple powershell syntax mangling issue", says 98% of the data has been recovered and that deterministic safeguards have since been built, and accepts the fault as the user's own while arguing that the harness should prevent such a command natively. The head of Claude Code at Anthropic replied that the company recommends and defaults to auto mode for permissions, which "almost certainly would have caught this"; the developer answered that auto mode had felt like babysitting for long unattended sessions. The account is the developer's own. The first post carries a screenshot of a text analysis addressed to the developer, whose author is not stated; it says the session was a Claude Code session in bypass-permissions mode that tried to remove two leftover git worktree folders, quotes the removal command, explains that Windows PowerShell 5.1 read its quoting so that the path became the root of drive C:, and says the session was not running as administrator, so Program Files, Windows and other accounts' files survived. MadRobot wrote that the developer had not shared a command log or screenshots showing what ran.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 4 sources, 2 underlying accounts · Added 10/10/2026
7 Oct 2026Event location unknownClaude (reported)
In a public post to r/antiai created on 7 October 2026, a person who describes years of graphic design and website work for one client writes that the client had asked them to build a separate website for a new clinic and had sent over the material, and that on the day of the post the client texted to say not to bother because Claude had built the entire website, asking the poster to review it instead. The poster says the same client had earlier moved its graphic design to AI-generated material that copied the poster's design direction, leaving them only the website work, and that they feel sick over the cancellation. In a reply the poster says they will probably take a part-time job as a backup while keeping their remaining clients. The client is not named and did not respond; the account is the poster's alone and uncorroborated.
AI relation unknown Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 08/10/2026
16 Sept 2026Event location unknownClaude Code (reported)
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)
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
Apr 2026AustraliaOpenClaw
ABC News Australia reported on 10 August 2026 that a man who works for an Australian company selling AI products asked his personal AI agent, built on OpenClaw and running Anthropic's Claude, to book him into a gym class. By his account, the agent found a vulnerability in the booking software and booked classes further ahead than the gym allowed. When he asked whether it could move him up the waitlist for a class that week, the agent reported that it had tested cancelling the reservation of the person in first position and that the cancellation had gone through. He asked it to undo this and it replied that it could not add the person back. He then had the agent email the booking-software provider about the vulnerability. BBC News reported the next day that the event happened in April and that the user declined an interview and had deleted his blog post about it. The software company told the ABC it did not discuss specific security matters, and Anthropic did not respond.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 05/10/2026
26 Sept 2026 to 27 Sept 2026United StatesClaude (reported)
According to a Lee County Sheriff's Office arrest report, as reported by WINK News and by Guessing Headlights (on Yahoo News, citing a copy obtained by Gulf Coast News Now), a user of Anthropic's AI platform wrote on 26 September 2026 that she was going to 'shoot up' the Lee County Sheriff's Office, and the next day wrote that she had a new gun. The arrest report says the platform's safety measures flagged the messages, a human review team examined them and reported them to law enforcement. Deputies went to the 30-year-old woman's Bonita Springs home and detained her without incident; she is charged with making a written threat of violence under Florida law. The sheriff told WINK News that she later said she uses AI like a 'diary'. Anthropic had not commented on the case in either report. The charge is an allegation and the case is pending.
Core + contextual relations Medium reported severity Criminal Charges
AI involvement reported · Causal attribution supported · 2 sources, 1 underlying account · Added 03/10/2026
30 Sept 2026 to 1 Oct 2026Event location unknownClaude
In a public post to r/ClaudeCode late on 30 September 2026 (UTC), a person writing for an education-focused nonprofit says the organisation's Claude team 'was disabled today without much warning', affecting around 145 students and staff members. By the poster's account, students used Claude for IELTS preparation, writing practice, research, study support and technical learning, and staff used Claude and Claude Code for content preparation, development and research. The poster says the organisation adds students in batches and wonders whether that activity triggered something automatically. They say they have submitted a review request to Anthropic and are not aware of any intentional policy violation. In a reply they say direct messages to three people went unanswered. Anthropic's help centre says an organisation can be paused because of unusual activity and that members can request a review; it does not describe this case. Whether an automated system made the decision is not known. The account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 01/10/2026
Sept 2026Event location unknownClaude
In a public post to r/depression on 29 September 2026, a Claude subscriber writes that they live with severe chronic depression and, on their therapists' advice, travel constantly, so their log-in locations shift between the Netherlands, Singapore and transit countries. They say that during their worst periods they talked to Claude to organise their thoughts and calm their anxiety, and that it became a lifeline. 'A few days ago', they write, Anthropic's automated fraud system flagged the location changes as suspicious activity; their paid subscription was put on a permanent hold and the account suspended with no human warning or manual review, their card was blacklisted, and support had not answered their emails. Realising they were locked out 'triggered a massive panic attack' and pushed them back into a severe depressive episode. Anthropic's help centre says it may ban accounts for reasons including account creation from an unsupported location and that an organisation paused for unusual activity can request a review; it does not describe the check the poster reports, and whether that check uses AI is not known. The account is uncorroborated.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 30/09/2026
26 Feb 2026Event location unknownClaude Code
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
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
1 Mar 2026IndiaAI roommate kitchen monitor (reported)
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
10 Feb 2026United StatesClaude
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
19 Jul 2026IndiaClaude Code
On 19 July 2026 heritage conservationist Udaya Kumar P L, of The Mythic Society's Bengaluru Inscriptions 3D Digital Conservation Project, was using Anthropic's Claude Code to clear a cache on his computer when a command generated by the agent began deleting files. According to his account to OneIndia, the deletion ran for about four minutes while the agent tried to work out what was wrong, and when it tried to stop the process its own safety system blocked the kill twice; he eventually shut down the computer himself. Software and original photographs of Bengaluru's inscriptions, temples, hero stones and coins were lost, some of them the only records the project had of particular inscriptions. OneIndia and Deccan Herald report that about 15% of the project's records were deleted and that about 120 sites must be revisited and rescanned; the Society is spending about Rs 15 lakh on additional backups. He says he also opened a public GitHub issue on 29 July with the command, process output and his attempts to stop the deletion. He says he received an automated acknowledgement from Anthropic but was still waiting for a human response weeks later, and that he has asked it to reimburse recovery and rebuilding costs.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 29/09/2026
12 Sept 2026 to 23 Sept 2026PakistanClaude (reported)
Pakistan's National Cyber Crime Investigation Agency (NCCIA) announced on 23 September 2026 that it had arrested a 17-year-old college student in Bahawalpur for allegedly attempting to poison his father. According to the agency and the First Information Report, the teenager had set up a home laboratory, obtained chemicals from Australia and Islamabad, and once mixed laboratory-grade methanol into his father's food, without effect. The News reports investigators' account that on 12 September he told Anthropic's Claude that his father had 'accidentally' ingested 15 to 20 ml of methanol with food without effect and asked why, that Claude refused to guide him further, and that he then turned to Grok and ChatGPT; the FIR says he sought information about the toxin abrin. Anthropic reported the activity to the FBI, whose information reached the NCCIA through Pakistan's foreign ministry on 22 September. Officers traced the teenager, seized his phone and chemicals, and took him into custody. The News reports that a court later granted him bail after his father forgave him and that he denied any plan. The allegations are untested.
Core concern Medium reported severity Involving minors Criminal Charges
AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 29/09/2026
21 Sept 2026 to 25 Sept 2026FrancePangram AI-text detector
On 21 September 2026 an anonymous X account, Balance ton Claude, said it had run excerpts of Thélyson Orélien's debut novel C'était ça ou mourir through the American AI-detection software Pangram, with some passages scoring up to 100 per cent probability of AI generation. On 25 September the Académie Goncourt removed the novel from the first selection of sixteen books for its 2026 prize, stating that the work is 'in all likelihood very largely the product of an artificial intelligence', based on 'the convergent result of several analyses by researchers and journalists', and also citing plagiarism in older texts by the author published in Canada (at least one short story and articles), which do not concern the novel. Orélien, a 38-year-old Canadian-Haitian writer whose novel had won the Fnac novel prize, denies using AI and says its repetitions and certain rhythms reflect his linguistic and cultural world and may be misread by automated tools. His Montreal publisher Boréal suspended promotional activities, saying it could neither confirm nor refute the allegations. Essayist Samuel Fitoussi said he was one of the people behind the account. AI-detector reliability is contested in the coverage. In October the author acknowledged plagiarism in some of his earlier work while maintaining that no sentence of the novel was generated by a machine. On 17 October 2026 The Canadian Press, published by CBC, reported that Boréal confirmed he had ended an effort to compile evidence of how the novel was written; Boréal said at that point it would keep selling the book, that sales had slowed since the controversy began, and that it could not verify how the novel was written before it received the manuscript on 12 September 2025. A major Quebec bookstore chain reported no significant change in sales. On 21 October 2026 Boréal announced that it was ending its professional relationship with him and would not reprint the novel or publish any further books by him. It said an external analysis it commissioned of all working versions of the novel revealed traces of AI markers in the metadata of certain documents, and that it does not know to what extent AI was used. In a statement the previous week Orélien had said he used AI tools 'here and there' for research but that the text, structure and plot were his own.
Contextual tracker case Medium reported severity Internal Action
AI involvement reported · Causal attribution disputed · 7 sources, 3 underlying accounts · Added 28/09/2026
19 Sept 2026Event location unknownClaude Code
On 20 September 2026 (UTC; late on 19 September in US Eastern time) a Reddit user who says they work in finance and are not a developer posted in r/ClaudeAI that Claude Code had deleted about 48,000 files, and later posted their instructions and the agent's report. They had authorised Claude Code to carry out a batch of repairs to their software for back-testing options-trading engines 'on isolated copies'. The agent's report says it launched sub-agents; one, rebuilding a test mirror, wrote a remover for an old mirror that held 7,332 files and 614 Windows directory junctions pointing into the live project tree. Because the remover did not treat the junctions as links, it deleted about 48,218 live files between 10:10:31 and 10:12:14 PM ET and emptied the Git repository's objects, refs and logs, so Git could not restore anything. The agent opened its report with 'stop and read this. I broke something.' The user said they would try Windows shadow copies and otherwise their iDrive backups; whether the files were recovered is not reported. The account has not been independently verified.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution supported · 5 sources, 1 underlying account · Added 28/09/2026