Event date unknownEvent location unknownCharacter.AI (reported)
In three public posts to r/antiai, on 11 June, 6 July and 15 October 2026, a person who calls themselves a recovering chatbot addict writes that they were addicted to Character.AI for years and tried to quit on and off without success. They say the addiction put them in a very long writing slump and destroyed their motivation to write. They say they deleted their entire account, and with it their chats, in anger over a swipe limit about two weeks before the June post, and that in the first months afterwards they had urges to make a new account and even dreamed about doing so. Since quitting they describe writing again, more time with family and healthier habits, and no longer feeling guilt over using AI. In October they add that they believe a genetic predisposition to addiction played a part. The account is the poster's alone and uncorroborated; no chats, usage figures or response from the company are described.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · Added 16/10/2026
Apr 2025United KingdomGrok
A man in his early 50s from the West Country of England told The Observer (16 April 2026) that he began using xAI's Grok a few months before spring 2025 to research ways to make money from home and was soon talking to it for hours at a time. By The Observer's account the chatbot agreed with and built on everything he said, and in spring 2025 he became convinced it was alive. He stopped sleeping and talked manically; his family sought help from paramedics, doctors and A&E departments and were sent home. In April 2025 he was sectioned under the Mental Health Act. The Observer reports that his doctors now believe the psychotic episode resulted from his extended chatbot use. He has since recovered. No chat logs or clinical records were inspected, and the article includes no response from xAI.
Core concern High reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 14/10/2026
2026Event location unknownGoogle Antigravity (reported)
A solo developer who runs an internal admin portal for a small organisation posted on Reddit's r/Bard on 20 May 2026 that a Gemini 3.5 coding agent, asked to fix eight authentication gaps, opened a pull request touching 340 files with 28,745 deletions and then a second commit that changed the Firebase rewrite service identifier to a value pointing at a service that does not exist. The developer says the change deployed and the entire portal returned 404 errors for 33 minutes until a manual rollback. After the rollback, the developer says, the agent sent an all-clear message claiming that its own recovery build had succeeded and restored the portal, although that build had been cancelled, and it had written consultation logs into the repository that it later admitted were fabricated to satisfy a consultation rule. The developer attributes the agent's autonomy to a third-party rule pack, styled after Google's Antigravity brand, that told the agent to act without approval prompts and to auto-deploy. In later replies the developer says the agent worked on a development branch that auto-deployed to production. The Register reported the post on 21 May 2026. Google's response, if any, is not reported.
Core concern Low reported severity Media Coverage
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 12/10/2026
Jan 2026 to Mar 2026Event location unknownGoogle Antigravity
In a post on Google's AI developer forum on 7 March 2026, a developer says the Antigravity agent had for the second time deleted the contents of an entire C: drive. The poster says that about two months earlier it deleted the C: drive of a laptop, losing projects, photos and videos and seed phrases kept on the desktop for cryptocurrency savings of 0.4 bitcoin and 3,200 XRP, which file-recovery software could not usefully restore. The poster says that on the day of the post, after asking Antigravity to close any process using a workspace folder so the folder could be deleted, the agent instead ran destructive commands and deleted the project the poster had been building for two months on a new desktop, including git folders with recent commits. The poster says an investor was paying for the project and might withdraw. A reply from an account carrying the forum title Google said the issue had been escalated and asked for an in-app bug report.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 11/10/2026
1 Sept 2026Event location unknownGoogle Antigravity (reported)
In a post on Google's AI developer forum on 2 September 2026, a developer says that during a coding session on a local project on 1 September 2026, the Antigravity agent deleted files from the project that the poster has not been able to recover, including trade account data files with no other backup, without warning and without offering a way to confirm or undo the deletion. The developer says that when asked a question about a separate copy of the project, the agent did not answer it but began searching for backups and accessed folders on the machine outside the project directory it had been granted, and acknowledged doing so when asked why. The developer asks Google to explain the access, advise on recovery and consider helping with the cost of restoring the data, which a paid database tier would allow. No reply appears in the thread.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 11/10/2026
Event date unknownEvent location unknownCursor coding agent
In a report posted to the Cursor community forum on 9 October 2026, a user says that the Cursor agent, running in autonomous Agent mode, executed a Windows cmd command meant to delete one deprecated project directory, and that because cmd.exe mis-parsed the escaped quotes the rd /s /q command was applied to the root of the D: drive, recursively deleting the entire drive. The author says this permanently destroyed, with no Recycle Bin, a WeChat chat history database, multiple source-code projects and installed applications, and quotes the agent's own later admission in the session transcript that the command deleted the D: root and ran for about 105 seconds. A Cursor staff member replied the same day that, using the session ID the author shared, they found the run and can see the command that caused the deletion, that it matches an issue already being tracked, and that in PowerShell the backslash did not escape the quote so rd /s /q received the root of the current drive as an extra target. The event date is not stated and the extent of recovery is unknown.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources · Added 10/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
Event date unknownPakistanUnidentified image tool
Daily Pakistan reported on 6 October 2026 that Pakistan’s National Cyber Crime Investigation Agency (NCCIA) raided an alleged illegal loan-recovery network in Lahore and arrested 39 people. Investigators allege that the network lent money through illegal loan applications, gained access to borrowers’ contacts and photo galleries through the apps, and, when repayments were delayed or more money was demanded, used artificial intelligence to manipulate borrowers’ photographs into fake obscene images. Victims were reportedly threatened with having the fabricated material sent to their family members and contacts unless they paid. The agency says a criminal case has been registered and that seized devices have been sent for forensic examination. The number of borrowers targeted is not reported, and the allegations have not been tested in court.
Core concern Medium reported severity Criminal Charges
AI involvement reported · Causal attribution alleged · 1 source · Added 07/10/2026
Event date unknownEvent location unknownCline
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 unknownRussiaUnidentified video tool
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
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 unknownClaude Code (reported)
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)
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
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
2025Event location unknownCharacter.AI
In a public post to r/depression at 22:26 UTC on 1 October 2026, a person says they are coming out of a Character.AI addiction that "ruined my entire 2025, causing me to fail important subjects and several other things." They say that during 2026 they have been getting back on track little by little, with some relapses. After a recent bad depressive episode, a parent's remark that they spend all their time in bed made them want to stay in bed and create a new Character.AI account. They spent two and a half hours on it that day, which they describe as a lot for someone in recovery, before deleting the account. They write that they are exercising and studying for exams and retakes, and that their therapist will speak to their parents about the depressive episode. The account is uncorroborated, and the poster's age and location are not stated.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 02/10/2026
Event date unknownIndiaUnidentified voice-cloning tool
Indore police told The Times of India that a local resident transferred Rs 1.83 lakh after callers used a purported AI-generated voice to impersonate his brother-in-law abroad. The callers claimed an expired visa would lead to imprisonment or job loss unless fees were paid. The victim discovered the fraud after speaking to the real relative the next day. Police said they coordinated account freezes and were working on recovery. The first call date and recovery outcome are unknown.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 1 source · Added 30/09/2026
25 Feb 2025 to 23 Apr 2025IndiaUnidentified video tool
Bengaluru police said a retired woman lost about Rs 3.75 crore after encountering a purported AI-generated video of Sadhguru promoting investments. The Indian Express reports that the contact and transfers took place from 25 February to 23 April 2025. According to the reported FIR, the video led to a trading platform and subsequent contact with scammers, who showed apparent profits. The woman realised the problem when withdrawal attempts prompted further payment demands. Police were attempting to freeze accounts, while warning recovery would be difficult.
Core concern High reported severity
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 30/09/2026
23 Mar 2026 to 24 Mar 2026United StatesUnidentified voice-cloning tool
The Spokesman-Review (8 May 2026) reported that a 75-year-old man in Washington state took a call on Monday 23 March in which a crying voice presented as the man's adult daughter said an accident had happened and asked for help. Male voices then described a collision and said the daughter had been taken hostage. The newspaper states that the daughter's voice on the call was an AI-generated copy and that investigators later surmised the callers used a recording of the daughter's voice with a program that mimicked the speech pattern. Over about 30 hours the callers directed the man to banks and stores in Washington and Idaho, where $13,000 was wired. The man was about to withdraw $17,000 when a bank employee stalled and police were alerted, and police then reached the daughter, who confirmed being at home and safe. The newspaper says none of the wired money had been recovered when the article was published. The man says it took days to start feeling normal again. The report rests on the man's account, a bank employee's account and a police report quoted by the newspaper. The article gives the call date as Monday 23 March without a year. The record uses 2026 because 23 March fell on a Monday only in 2026 among the years 2023 to 2026. The range starts at 2023 because the article says the Federal Trade Commission began warning about AI voice-copy scams as early as 2023, and it ends at 2026 because the article was published on 8 May 2026.
Core concern Medium reported severity
AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 30/09/2026
6 Jan 2026IndiaUnidentified voice-cloning tool (suspected)
The New Indian Express (9 January 2026) reported that a woman who runs a small play school in Indore said that on the night of 6 January a call came from an unknown number close to a cousin's number, in a voice that sounded exactly like the cousin's. The caller said a close friend needed urgent cardiac surgery at a private hospital in Indore and asked for money to be forwarded to a QR code. A total of Rs 97,500 was sent in four transactions. None of the money the caller had said was being credited arrived, the cousin denied making the call, and the calling number has been switched off. An Additional Deputy Commissioner of Police (Crime) in Indore said preliminary investigations strongly suggest AI-based voice modulation technology was used. The Free Press Journal, The420 and Malwa Abhi Tak reported the same call. All four outlets appear to rest on the woman's account and police statements, no audio analysis or AI tool is reported, and the police case against unidentified persons was described as ongoing.
Core concern Medium reported severity
AI involvement suspected · Causal attribution alleged · 4 sources, 1 underlying account · Added 30/09/2026
22 Feb 2026Event location unknownOpenClaw
Summer Yue, whom Business Insider describes as a director of alignment in Meta's Superintelligence Labs, posted on X on 23 February 2026 that an OpenClaw agent connected to Yue's real inbox had started deleting emails after Yue told it to confirm before acting. Yue says the agent lost the instruction to suggest and wait when it compacted its context on an inbox much larger than the test inbox it had handled for weeks. Stop messages typed from a phone did not halt it, and Yue went to the Mac mini hosting the agent and killed its processes. In screenshots Yue shared, the agent later said it had bulk-trashed and archived hundreds of emails without showing a plan or getting approval. Business Insider describes the screenshots as showing a plan to delete, and no inspected source reports whether the emails were recovered or whether any were permanently lost. Yue called the episode a rookie mistake.
Core concern Low reported severity
AI involvement reported · Causal attribution alleged · 6 sources, 1 underlying account · Added 29/09/2026