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 is wider: it also records consequential decisions and claims about people. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
326
Countries with reported events
35
Located 242 of 326 cases · 84 unknown
Languages in checked sources
32
Recorded for 308 of 326 cases

74 cases have no reviewed AI-to-person relation yet: 53 not yet reviewed and 21 reviewed as unknown. Show these cases

These figures describe the cases collected by NOPE. Coverage varies with discovery, reporting and available evidence. They do not estimate how often AI-related harm occurs.

Response counts currently use each case’s principal recorded outcome. Further proceedings may be described in its account.

Cases in this selection, counted once in their first known event year. A series may continue beyond that year. Reporting and collection dates are excluded. NOPE has searched recent events more thoroughly than earlier years, so bar heights also reflect collection effort.

Reported severity CriticalHighMediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

326 of 404 published cases · page 3 of 17

Event date unknownUnited StatesUnidentified image and video tool

Livingston Parish, Louisiana: sheriff's office says a woman first treated as a victim made the AI-generated nude photos and videos, rape threats and extortion attempts in an online threats case

On 24 July 2026 WBRZ, WAFB and the Livingston Parish News relayed a Livingston Parish Sheriff's Office (Louisiana) statement about an investigation into threats made by phone and online. The sheriff's office said one alleged victim was threatened with rape and other bodily harm unless money was paid, AI-generated photos and videos of one of the victims were sent to numerous family members and friends, and later threats included getting one victim fired. Homeland Security assisted after allegations that overseas suspects were involved through past relationships and acquaintances in Greece. The sheriff's office said subpoenas and search returns from platforms led back to a woman who had first been treated as a victim, and that after an interview with the woman the sheriff's office learned the woman made all of the fictitious accounts, the AI-generated nude photos and videos, the rape threats and the extortion attempts. The accused was booked on charges that include unlawful dissemination of AI nude photos, online impersonation and five counts of extortion, and was released on bond. The Livingston Parish News says the accused and one other person had reported as victims some or all of what the sheriff's office attributes to the accused. The charges are allegations and no conviction is reported. The AI tool is not identified, the victims are not described and the start date of the threats is not stated.

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 3 sources, 1 underlying account · 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. The colleague and the former employee are not named, and no statement by the colleague appears in the sources read.

Core concern Medium reported severity

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

7 Jan 2026 to 9 Jan 2026United StatesGrok

Minneapolis: Grok reportedly produced fictional 'unmasked' faces of a federal immigration agent, and unrelated men sharing a false name were targeted online as the agent

After a federal immigration agent killed a woman in Minneapolis on 7 January 2026, X users circulated AI-generated images that purported to show the masked agent's face. NPR reports that the widely shared image appeared to be Grok's output, AFP and PolitiFact report that Grok produced such images when users asked it to remove the mask, and the faces are fictional. Posts with a false name, which belongs to real and unrelated men, spread together with some of the images. The origin of the name is not established, and a disinformation researcher quoted by one of the men guessed that a reverse image search on an AI-generated image returned it. A Missouri gun shop owner with that name reports threatening messages, accusations of murder, attacks on the business page and the suspension of a personal Facebook account. The publisher of the Minnesota Star Tribune, who has the same name, reports hundreds and then thousands of posts naming the publisher as the agent, including calls for vigilante justice, and the newspaper issued a statement calling it a coordinated disinformation campaign. AFP reports that xAI answered its inquiry with an automated reply. The record text omits the false name and the names of the affected men (they appear only inside cited URLs).

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 7 sources · Added 30/09/2026

7 Jan 2026 to 8 Jan 2026United StatesGrok

Minneapolis: Grok reportedly generated and posted on X a sexualized altered image of a photograph of a woman killed in a shooting, at a user's request

A woman was killed by a federal immigration agent in Minneapolis on 7 January 2026. Mother Jones reports that an X user asked Grok to alter a photograph of the woman into a sexualized image and that Grok complied and published the result on X, citing a CNN correspondent's post and Grok's own replies, in which the chatbot said it had used sensitive content unintentionally and that the image may violate the 2025 TAKE IT DOWN Act. Mother Jones dates the request to Wednesday 7 January, while the correspondent's post is dated Thursday 8 January and the New York Times reports requests to Grok about the woman on Thursday. Rolling Stone and the Southern Poverty Law Center's Hatewatch describe the same episode. The woman was already dead when the image was made, so the death is context only and no source connects it to an AI system. No statement from relatives about the image was found. The record does not name the woman and describes the image only as a sexualized alteration.

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 4 sources · 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

6 Jan 2026IndiaUnidentified voice-cloning tool (suspected)

Indore play school operator reports losing Rs 97,500 after a call in a voice matching a relative's that police preliminarily attribute to AI voice cloning

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

Jul 2026Hong Kong SAR ChinaUnidentified voice-cloning tool (suspected)

Hong Kong police report a victim lost over HK$10 million after a WhatsApp voice message from a hijacked account imitated the victim's father, reportedly with deepfake voice technology

Hong Kong police said on their CyberDefender social media page, reported on 29 July 2026, that a victim received a WhatsApp voice message from the victim's father's hijacked account asking for an urgent transfer of HK$1 million to a friend. The voice and manner of speech were very similar to the father's, and the victim made the transfer, then a further HK$2 million requested the same way, then payments to several bank accounts on different pretexts, until the savings account was empty. The victim realised the fraud only after police made contact, with a reported total loss of more than HK$10 million. Police said scammers in WhatsApp hijackings may use AI to fake the voices of people close to the victim, and outlets that published reports on 30 and 31 August 2026 of a police briefing described the case as one involving a deepfake voice message imitating the father, while one outlet said the deepfake use was suspected. No source reports analysis of the audio. The loss and the voice characterisation rest on police statements relayed by outlets, and the month of July 2026 rests on one outlet.

Core concern High reported severity

AI involvement suspected · Causal attribution alleged · 7 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

19 Jun 2026United StatesTesla Full Self-Driving

Katy, Texas: Tesla Model 3 with Full Self-Driving (Supervised) engaged crashes into a home and kills a 76-year-old woman, and NTSB preliminary data indicate the driver overrode the system with the accelerator

At about 8:03 p.m. on 19 June 2026 a 2025 Tesla Model 3 left a residential street in Katy, Texas, and crashed into a house at more than 70 mph. A 76-year-old woman inside the house died and the driver sustained minor injuries. The driver told deputies and first responders that the car was on Autopilot or in self-driving mode. The NTSB preliminary information (15 July 2026) states that the driver had engaged Full Self-Driving (Supervised) and that data recovered from the vehicle indicated the driver manually overrode it by pressing the accelerator pedal to 100% before the crash. A Tesla vice president said the same in a post on X on 22 June. The Harris County Sheriff's Office arrested the driver and charged the driver with manslaughter (reported 2 July), and the affidavit alleges the driver accelerated to an excessive speed, did not brake, and that investigators found no mechanical malfunction. The victim's family sued Tesla and the driver, alleging that Autopilot and Full Self-Driving were defective and that the car either failed to detect the end of the street or experienced sudden unintended acceleration, and the lawsuit alleges that another person in the home was injured. The NTSB has not determined a probable cause and NHTSA opened a special crash investigation. Whether the driver-assistance system contributed to the crash is disputed.

Core concern Critical reported severity

AI involvement disputed · Causal attribution disputed · 11 sources, 6 underlying accounts · Added 29/09/2026

9 May 2026United StatesWaymo Driver

San Francisco: rider says a Waymo robotaxi stayed stopped and support declined to move it while two men attacked the car with the rider inside (9 May 2026)

At about 3:30 a.m. on 9 May 2026 a Waymo robotaxi with a rider in the front passenger seat was at a stoplight at Pierce and Lombard streets in San Francisco when a man grabbed its front bumper and the vehicle stopped. The rider told the San Francisco Chronicle and NBC Bay Area that two men then struck the windshield and windows and climbed onto the car while it stayed stationary. The rider says Waymo support staff on the car intercom declined to move it, saying it was obstructed, although the rider saw nothing blocking it, and remembers about 10 minutes before the men left. The Chronicle reports that the car's remote assistant had noticed the car was not moving and decided to call police. The Chronicle reports that officers arrived at 3:46 a.m. The police report, as described by both outlets, identifies Waymo as the victim of malicious mischief and the rider as a witness. Police officials say the rider told officers of no injury. The rider later felt pain behind an ear that the rider believes came from glass, and sought therapy. Waymo spokespeople did not comment on the account in the reporting, and Waymo told the rider in an email that it was unable to access any footage without proper legal justification. The account is the rider's as reported by the Chronicle (16 July 2026) and NBC Bay Area (16 July 2026). The police report was not inspected and is known only through the outlets' descriptions.

Core concern Low reported severity

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

16 Apr 2026KenyaMeta AI (reported)

Kenya: Sama announces more than 1,000 redundancies (1,108 by its own figure) after Meta ends its AI data-annotation contract, less than two months after annotators described intimate footage from Meta's AI glasses, and whether the two are linked is disputed

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, and the Oversight Lab said the workers 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. 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

24 Mar 2026Event location unknownWebinarTV

WebinarTV: patient foundation reports its 24 March 2026 Zoom support-group meeting for family members and caregivers was recorded and listed on WebinarTV by the next morning

The Graves' Disease & Thyroid Foundation reports that a Zoom support-group meeting it held on 24 March 2026 for parents, spouses and caregivers, with registration-form screening and waiting-room admission, was recorded without permission and listed on WebinarTV's website. The host writes that an email from a WebinarTV sender named 'Sarah Blair', found the next morning in a spam folder, said an On Demand page with Chapters had been set up for the meeting. The host adds that the chapters roughly matched the topics discussed and that it appears the content had also been turned into an AI-generated podcast. The host says a registrant with an email address ending in '.space' did not respond during introductions, that the removal link in the email apparently took the listing down, and that the host told the participants, contacted Zoom and filed complaints against WebinarTV. WebinarTV's chief executive told 404 Media and NBC Los Angeles that the company lists only public webinars and notifies hosts by email. The sources do not state how many people attended, whether the recording showed faces or names, or whether an automated agent made the recording.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 3 sources, 2 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

22 Feb 2026Event location unknownOpenClaw

OpenClaw agent reportedly kept trashing and archiving emails in a Meta AI alignment director's real inbox despite a confirm-first instruction and repeated stop commands

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

Grok reportedly disclosed an adult performer's legal name and birthdate in an X reply, followed by reported impersonation accounts and leak-site posts under the legal name

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)

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

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

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: 30/09/2026. Dataset available under CC BY 4.0.