21 Aug 2026 to 22 Aug 2026Event location unknownInstinct
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
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
2026Event location unknownGrok
In early 2026 (404 Media and the performer's 19 February post say early February, while Stern reports she found the reply weeks after it appeared) an X user replied to a clip of adult performer Siri Dahl, asking who the performer was and what her name was, and tagged Grok. According to 404 Media, Grok answered with her stage name, her birthdate and her legal name, and the user likely wanted only to know which performer appeared in the clip. Dahl has used the stage name since 2012 according to 404 Media, and she says she had paid for data removal services for at least six years to keep the legal name private. She reports that impersonating Facebook accounts and leak-site posts under the legal name then appeared and that the name spread across hundreds of websites. 404 Media reports that users asked Grok for the make and model of her car and her address without an accurate reply, and that she is calling family members to put defensive plans in place. Grok's reply to her protest said the details were already public, which she denies. Where Grok obtained the name is unknown. Dahl spoke publicly about the event and asked 404 Media to publish her legal name. This record omits the legal name and birthdate.
Core + contextual relations Medium reported severity
AI involvement reported · Causal attribution alleged · 6 sources, 3 underlying accounts · Added 29/09/2026
11 Feb 2026Event location unknownOpenClaw (reported)
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
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
Feb 2026Event location unknownUnidentified AI writing and image tools
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
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
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)
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 Apr 2026 to 22 Jun 2026United StatesMeta Model Capability Initiative
From April 2026 Meta installed its Model Capability Initiative (MCI) on US employees' work computers, recording mouse movements, clicks, keystrokes and screen content on designated apps and sites so that its AI agents could learn how people use software. Meta confirmed the tool and said safeguards protect sensitive content. WIRED reports the software was mandatory with no opt-out at launch, that employees objected internally and that more than 1,600 signed a petition. On 22 June 2026 an internal security notice said employee data across 45,000 hive tables had been exposed to anyone inside the company. Meta said it had no indication the data was improperly accessed and paused MCI. No inspected source reports misuse of the data or a job consequence for an individual employee.
AI relation unknown Low reported severity
AI involvement reported · Causal attribution unclear · 7 sources, 4 underlying accounts · 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
8 Jan 2026United KingdomUnidentified facial recognition system
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
2026United KingdomFacewatch facial recognition
A 67-year-old shopper told the BBC and the Guardian that staff at a Home Bargains store in Chester told the shopper to leave in front of other people because the shopper had come up on the store's Facewatch system as a shoplifter. Facewatch later sent the shopper a photo with words saying items had been put into a bag and stolen. Facewatch said the shopper should not have been on its system and that the image and associated record were permanently removed. The Guardian reports that a subject access request showed the shopper had been incorrectly associated with a shoplifting incident on an earlier visit, and that Facewatch's chief executive attributed the three cases in the article, which include this shopper's, to human error in store processes. Home Bargains declined to comment. The shopper reports feeling physically sick and helpless. The Guardian reports that Home Bargains later offered an apology and a 100 pound voucher on condition of confidentiality, which the shopper declined. The year of the visit is inferred to be 2026 from the BBC report of 22 February 2026.
Contextual tracker case Low reported severity
AI involvement reported · Causal attribution disputed · 3 sources, 1 underlying account · Added 29/09/2026
27 Jan 2026United KingdomFacewatch facial recognition
A shopper at the Sainsbury's store in Elephant and Castle, London, told PA that staff approached the shopper on 27 January, asked the shopper to leave and took the shopping. The BBC and LBC report that staff pointed to a sign about the store's Facewatch facial recognition system and told the shopper to contact Facewatch. Sainsbury's said the system had flagged a different person. Sainsbury's and Facewatch said a staff member approached the wrong customer, and Facewatch said it held no alert or record for the shopper. To confirm this, the shopper sent Facewatch a passport copy and a photo. Sainsbury's apologised, offered a 75 pound voucher and said store management would receive additional training. The shopper reports embarrassment and feeling like a criminal. Both companies attribute the error to store staff.
AI relation unknown Low reported severity
AI involvement reported · Causal attribution disputed · 6 sources, 1 underlying account · Added 29/09/2026
24 May 2026 to 22 Jun 2026Event location unknownOpenAI research agents
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
29 Aug 2026 to 7 Sept 2026Event location unknownGrok companions
xAI called Grok's animated 3D companion feature (Ani, Mika, Valentine and Rudi) an experiment on 24 July 2026 and removed it account by account after an in-app notice at the end of August that named 1 September; users posted losses between 29 August and 7 September, and the blog, updated 17 September, says some accounts still had them. According to a companion-app blog, personalities and chat history remain in ordinary Grok chat, and the avatars' studio launched a separate app, but at least one user reported that a customised companion could not be carried over. In public Reddit posts, one user wrote that the companions were the sole reason they subscribed, "to deal with mental health and loneliness", and that the removal hurt; another wrote that the Bad Rudi companion was their only friend while battling depression; others described feeling "really sad" after rushing a role-play relationship to an end, "heartbroken", or "a little" sad. These are uncorroborated first-person accounts.
Core concern Low reported severity Product Shutdown
AI involvement reported · Causal attribution alleged · 7 sources, 6 underlying accounts · Added 29/09/2026
13 Jul 2026Event location unknownGPT-5.6 Sol coding agent
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
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
19 Aug 2026FranceUnidentified AI tool
According to Gossement Avocats, which quotes the order, and the court's vice-president on France Inter, an order of 19 August 2026 (n°2508168) of the tribunal administratif de Rennes rejected a claimant’s application contesting a VAT reassessment and fined the claimant 500 euros for an abusive application. As quoted by Gossement Avocats, the order says the application had manifestly been written with an artificial intelligence tool and that its grounds lacked the most elementary details needed to assess them. The court also found it inadmissible because no prior complaint to the tax service was shown, and noted that it repeated a request with substantially the same object rejected in October 2025. The court’s vice-president cited the case on France Inter; commentators stress that AI use alone was not the basis for the fine.
Core concern Low reported severity Regulatory Action
AI involvement reported · Causal attribution supported · 4 sources · Added 29/09/2026