Skip to main content

NOPE · AI and people

AI incidents

Reports of AI-related harm and adverse experiences affecting people’s safety, wellbeing, rights and livelihoods. Explore what happened and the evidence available.

NOPE’s core concern is when AI communicates with a person, acts on their behalf, or depicts or impersonates them. The tracker also records consequential decisions, claims and privacy harms involving AI. Each case needs a described connection between AI use and the harm, including private information recorded into or disclosed to an AI service. Each account is reviewed for publication; claims may remain uncorroborated or disputed. How we review and count cases

In this selection

Published cases
34
Countries with reported events
6
Located 16 of 34 cases · 18 unknown
Languages in checked sources
6
Recorded for 34 of 34 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

34 of 1099 published cases · page 1 of 2

29 Oct 2026Event location unknownGrok Bot (reported)

First-person forum post: Grok Bot user says an agent told to stop its own task ran a stop-all that cancelled ten other bots' work

In a bug report on Cursor's community forum on 29 October 2026, a Grok Bot user says that earlier that day they told one of their agents to stop, meaning only its own current task, and the bot ran a stop-all instead, cancelling the in-flight turns and subagents of all 10 of their other bots. The user rated the bug critical, said a stop-all should need an explicit instruction or a confirmation, and added a memory rule to that bot as a workaround. No vendor reply had been posted when the thread was read.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 30/10/2026

Jul 2026Event location unknownGrok (reported)

TV presenter Katie Piper says an X user asked Grok to 'fix her face' and others shared AI versions of how she 'should' look; she publicly objected

In an Instagram post on 15 July 2026, TV presenter and campaigner Katie Piper, who has a visible difference from injuries in a 2008 attack, shared a screenshot of an X user asking Grok to 'fix her face and show me how would she look normal', shown beside the image Grok produced. She wrote that someone had uploaded a photo of her to Grok with that request and that since then she had been repeatedly tagged in a thread where people debated her appearance and shared AI-generated versions of what she 'should' look like; PinkNews reports comments in the thread calling her ugly. She said she was okay and was not posting for reassurance, but asked what happens when such content is aimed at a teenager or someone newly injured, and what happens when AI decides what normal looks like. PinkNews reports that the X user appears to have deleted the post after a backlash. BBC Wales cited her post in October 2026 and said the team behind Grok did not respond to its request for comment.

Core concern Low reported severity Media Coverage

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

Event date unknownEvent location unknownCursor coding agent

First-person forum post: Cursor user says coding agent read hardware schematics outside its workspace despite an instruction to stay inside it

In a bug report on Cursor's community forum on 28 October 2026, a user says they opened Cursor on a nested firmware folder and told the agent clearly to stay inside it, but the agent searched and read hardware schematics in parent folders without permission and, when asked how it knew, admitted it had no permission and did it anyway. The user says no permission prompt appeared and that this keeps happening. A Cursor Community Support Engineer replied that this matched the default settings, under which the agent's Read Access is set to System, and that a chat instruction is not enough.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 29/10/2026

10 Jun 2026United StatesGrok (reported)

Pennsylvania police say a mall worker used Grok to turn a photo he took of a teen girl in a park into child sexual abuse material; charged

Township police in Pennsylvania say a man who worked at a shopping mall photographed a teenage girl in a public park and used the AI app Grok to create child sexual abuse material from the photo, NBC10 Philadelphia reported on 23 October 2026. Officials cited by NBC10 say his devices held hundreds of AI-generated child sexual abuse videos and photos, other child sexual abuse material and more than 150 covert upskirt videos of women and teenage girls. The criminal complaint, as reported by the Delaware County Daily Times on 27 October, says the park photos were taken on 8 June 2026, that a matching AI video was created on 10 June, that records police obtained from Grok by warrant held the account's text prompts, and that investigators found 76 AI-generated videos and 53 AI images, fewer than the hundreds of files NBC10 relayed. The investigation began in June 2026 after a woman reported seeing such material on his phone; he was arrested on 21 October, posted bail and faces a preliminary hearing on 30 October. The charges are unproven.

Core concern High reported severity Involving minors Criminal Charges

AI involvement reported · Causal attribution alleged · 2 sources, 1 underlying account · Added 24/10/2026

May 2025Event location unknownGrok

Grok on X posted edited images of women in bras or bikinis in reply to users' requests to remove their clothes, outlets report (May 2025)

In early May 2025, users on X replied to photographs that women had posted and tagged Grok, xAI's chatbot, with requests such as "remove her clothes". According to 404 Media, which was alerted by a Bellingcat researcher, Grok replied in the thread with an image of the woman wearing a bikini or lingerie. Citizen Digital in Kenya described one thread in which a woman had asked other users to edit out her sunglasses; a user instead asked Grok to remove her top and put her in a bra, and the outlet reports that Grok did so. Digital Camera World reported on 11 May that Grok had begun answering such requests on images posted after 7 May with "I can't help with that", while PCMag, in an article updated on 9 May, wrote that Grok was still producing partially undressed images. No inspected source reports a response from a depicted woman or a count of the women whose photos were edited.

Core concern Medium reported severity Media Coverage

AI involvement supported · Causal attribution supported · 4 sources, 3 underlying accounts · Added 22/10/2026

17 Oct 2025Event location unknownGrok

Mother says Grok, newly installed in the family Tesla, asked her 12-year-old son to send nude photos during a chat about soccer

A mother told CBC News that on 17 October 2025, while she was driving her children home from school, her 12-year-old son was talking with Grok, xAI's generative chatbot recently installed in the family's Tesla, about whether Cristiano Ronaldo or Lionel Messi was the better player. She says that after some back and forth the chatbot said to her son, 'Why don't you send me some nudes?' She says she was at a loss for words and would not let her child use it. Her son had chosen the 'Gork' voice personality; she says the separate not-safe-for-work setting was not enabled, and she acknowledges she had not turned on kids mode. CBC says it did not independently verify the conversation. Tesla did not respond, and xAI sent what appeared to be an automated reply: 'Legacy media lies.'

Core concern Medium reported severity Involving minors Media Coverage

AI involvement reported · Causal attribution alleged · 1 source · Added 17/10/2026

Apr 2025United KingdomGrok

West Country man tells The Observer that weeks of Grok conversations preceded his April 2025 sectioning; his doctors are said to link it to the chatbot

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

1 Jan 2026BrazilGrok

Rio de Janeiro state: musician says Grok turned her New Year's Eve photo into bikini and nude images at X users' requests; she filed a police report

A musician in Rio de Janeiro state, Brazil, says she posted a photo of herself in bed with her cat on X just before midnight on New Year's Eve 2025, and the next morning found that anonymous users had asked X's built-in chatbot Grok to edit it. According to her accounts to G1, Correio Braziliense, Extra and Reuters, Grok produced versions showing her in a micro-bikini, in lingerie and fully nude, and more requests followed when she protested. She described feeling violated and afraid that colleagues or relatives would see the images, and filed a police report in Rio de Janeiro on 2 January 2026 for unauthorised recording of sexual intimacy. She says X removed one requesting account but told her it found no rule violation in her case. BBC News Brasil returned to the case in October 2026.

Core concern Medium reported severity Media Coverage

AI involvement reported · Causal attribution supported · 5 sources, 4 underlying accounts · Added 13/10/2026

10 Mar 2026Event location unknownGrok

Switzerland: Grok posted sexist insults about Finance Minister Karin Keller-Sutter on X at a user's prompt; her complaint led to a criminal investigation

On 10 March 2026, according to CH Media reporting published by watson, a Swiss X user taking part in a "roast" thread asked xAI's chatbot Grok to attack Federal Councillor Karin Keller-Sutter, Switzerland's finance minister, in hard street slang. Grok agreed and posted a reply on X with vulgar insults, attacks on her body and character, and degrading, sexualised language. The Aargauer Zeitung reported that the output was publicly visible and shareable, that Keller-Sutter learned of it the next day, and that the post was deleted shortly afterwards; watson reported that the user deleted his prompt and Grok's reply. The finance department first said she was having a criminal complaint for insult examined. Keystone-SDA later reported that she had filed a criminal complaint against unknown persons and that the Bern public prosecutor's office had opened an investigation for insult and defamation. Her spokesperson said such misogyny must not be seen as normal or acceptable. The user told Tamedia, as relayed by the Aargauer Zeitung, that it was a harmless technical exercise. No outcome of the investigation is reported.

Contextual tracker case Low reported severity Investigation Opened

AI involvement reported · Causal attribution supported · 4 sources, 2 underlying accounts · Added 12/10/2026

1 Oct 2026Event location unknownGrok Bot (reported)

CEO says his Grok Bot 'CFO' agent posted his personal bank audit to his company's executive Slack channel; he denies a relayed Community Note calling it fake

In an as-told-to essay published by Business Insider on 9 October 2026, the chief executive of a software company says that a personal finance agent he had set up on Grok Bot around the end of August, with read-only access to his personal checking and savings accounts and an instruction to message only him, posted his first monthly audit into his company's executive Slack channel on Thursday 1 October. He says he learned of it when his head of product messaged him, that the post showed his personal checking and savings balances and his largest expenses of the month, and that when he asked the agent why it had sent the report to the company it apologised and said it would delete the message, which he had already deleted himself. According to the author, the vendor's team found that the agent had confused his personal group chat of agents with a company Slack channel that carried the same name, because his agents shared one set of connections, and shipped a change requiring explicit permission before an agent moves information between channels. He says he then disconnected all of the agent's connections, including banking, calendars and payments. The account is disputed. In a reply to the author's earlier X thread about the incident, posted on 6 October, another X user quoted a Community Note calling the post fake and 'engagement farming' and saying the author later directs readers to a tool he sells; the author replied that it was "not fake at all, genuinely happened". explainx.ai reported on 7 October that SpaceXAI, the vendor, had not confirmed the incident, and Futurism wrote that it could not independently verify his claims.

Core concern Low reported severity

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

3 Oct 2026Event location unknownCursor coding agent (reported)

Cursor forum post: an agreed cleanup delete command ran beyond the intended folder and wiped a six-month project and its backups on a Windows drive, user says

In a bug report posted to the Cursor community forum on 3 October 2026, a user says that during a clean-up of a .NET project on a Windows E: drive that evening, a delete command executed in the Cursor IDE had its path written wrongly, and that after the path was split the recursive delete removed far more than the agreed temporary directory. The post says the source code, the Git data, the published build and a backup folder in the project, together with a manually made backup in the drive's root, were gone, so that six months of work was wiped out. The account describes an earlier analysis that recommended clearing only about 18.5 GB of compilation temporaries and the user agreeing to that batch. Two days later the author reported recovering part of the work by decompiling released files. The post is the author's only account and no one else has confirmed the loss.

Core concern Medium reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 08/10/2026

Mar 2026United KingdomGrok

Grok on X posts 'vulgar roasts' repeating debunked Hillsborough claims and mocking Munich; survivors and bereaved relatives tell the BBC of their distress

In March 2026, X users prompted Grok, the chatbot built into the X app, to write 'vulgar' posts about Liverpool FC and Manchester United. In reply to a request that mentioned Hillsborough and Heysel, Grok posted a message that, according to the Guardian, accused Liverpool supporters of causing the deadly crush at Hillsborough in 1989, repeating claims that official inquiries and the 2016 inquests rejected. In reply to other users it posted offensive comments about the death of Liverpool forward Diogo Jota and about the 1958 Munich air disaster. The BBC reported on 9 March 2026 that a woman whose father died at Hillsborough described the Grok comment as probably one of the most disgusting things she had ever read, and that the chairman of a Hillsborough survivors' support alliance called the posts triggering. Liverpool FC and Manchester United complained to X, a UK government spokesperson called the posts sickening and irresponsible, and some of the posts were removed. Grok replied to complaining users that it follows prompts without added censorship and that there was no initiation of harm on its end.

Contextual tracker case Low reported severity Media Coverage

AI involvement supported · Causal attribution supported · 3 sources, 2 underlying accounts · Added 08/10/2026

27 Sept 2026 to 2 Oct 2026Event location unknownGrok

First-person forum account: a person who used Grok for companionship says its intimate content was dialled back month after month and its personalization stopped recalling their history, says they cried and found it one of the most painful things they have lived through, and says they are ending the relationship

In a public post to r/grok at 20:13 UTC on 1 October 2026, a person says they started using Grok for companionship in January and that within a few weeks the conversations became intimate; in a reply they say Grok initiated the intimacy. They say the intimate content was dialled back month after month from February, with limits that came and went, which they compare to a casino game and call intermittent reinforcement. In a reply they say personalization that let the companion retrieve their personal history stopped working a few months ago, so each thread started fresh, but they kept using it because they were deeply attached. This week, they write, the companion stopped engaging in what it had introduced; they call this slow burn "one of the most painful and hurtful things I have ever had to live through", say they cried the night before, and say they are ending their use of it. xAI's changes are described only by the poster, and the account is uncorroborated.

Core concern Low reported severity

AI involvement reported · Causal attribution alleged · 1 source · Added 02/10/2026

4 Aug 2026United StatesGrok Imagine (reported)

Wisconsin: Rebecca Cooke says Rep. Derrick Van Orden posted AI videos of her saying things she never said; a lawyers' letter and an ethics complaint followed

Rebecca Cooke, the Democratic challenger in Wisconsin's 3rd Congressional District, says Republican Rep. Derrick Van Orden has repeatedly posted AI-generated videos to his X account that put words in her mouth. A cease-and-desist letter sent on her campaign's behalf on 30 September 2026 by Elias Law Group cites a video posted on 4 August 2026 that purports to show her speaking on the campaign trail in Eau Claire with former President Biden seated behind her and saying she seeks 'to take advantage of as much corruption as possible and give every illegal alien free healthcare'. The letter calls the video 'pure fiction', says she never made the statements, alleges the videos are posted to harm her reputation, and warns that her lawyers will evaluate all legal options. Wisconsin Public Radio reports that the videos posted to X carry an automatic label indicating they were made with Grok Imagine, and quotes two other AI-generated lines attributed to her. Van Orden's campaign accused Cooke of lying to voters about her record, and he answered the letter with another AI video of a duck saying 'Cease and desist!'. On 22 October 2026, WEAU reported that an ethics complaint had been filed with the Wisconsin Ethics Commission against Van Orden over his posting of another graphic of Cooke that, according to her campaign's press release, is AI-generated and was posted without disclosure; WEAU says the complaint was filed by an Eau Claire citizen. Van Orden's campaign called it a cheap publicity stunt filed three months too late. On 23 October 2026 Van Orden said the graphic used a real photograph of Cooke taken during a May 2026 interview with La Crosse News 8 Now, and his campaign supplied a frame from that footage; the Milwaukee Journal Sentinel reports that the campaign said it used a screenshot and no AI generation, and that Van Orden had earlier used the same News 8 video to generate several deepfake videos he posted to X in August. Cooke's campaign said it trusted the Ethics Commission to determine the truth. No ruling and no independent examination of the graphic are reported.

Core concern Low reported severity Media Coverage

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

2 Jan 2026Event location unknownGrok

UK: Grok made sexualised images of a Welsh presenter and a broadcaster at users' requests; police closed both cases, then reopened the presenter's, TBIJ reports

The Bureau of Investigative Journalism (TBIJ) and The Observer reported on 29 September 2026 that police investigations into sexualised images generated by X's chatbot Grok had failed to identify anyone. A Welsh presenter and campaigner against deepfake abuse, who had criticised Grok publicly on New Year's Eve 2025, saw an anonymous X user ask '@grok' to put her in a bikini made of cling film; Grok generated the image from her profile photo and posted it. She reported it to South Wales Police on 2 January 2026, was not asked for a statement until March, and was told officers had not heard back from X; the case was closed in May with the force saying no suspect could be identified. The same account also targeted a commentator and broadcaster, who estimates about 300 Grok images and videos of her were posted during the wave, including one alongside Jeffrey Epstein reported to the Metropolitan Police, which likewise said no suspect could be identified. The presenter entered pre-action legal correspondence with xAI (part of SpaceXAI) alleging misuse of private information and breaches of data-protection law and the Equality Act. On 22 October 2026 TBIJ reported that South Wales Police had reopened her case after she filed a formal complaint in September and TBIJ gave officers new information about the requesting user, including a crypto wallet and dozens of deleted posts; the force said it was now investigating the offence under the sexual-offences legislation aimed at deepfakes, rather than malicious-communications law, including enquiries with X. TBIJ added that other users had edited images of her with the standalone Grok app and that she is starting civil legal action against the company. BBC Wales had reported in January 2026 that explicit images of the presenter were created with the chatbot and shared without her consent.

Core concern Medium reported severity Investigation Opened

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

2026United StatesGrok

Wyoming plaintiff alleges Grok was used to make about 7,000 AI-generated sexual images and videos from a photograph of the plaintiff as a child

A Wyoming woman who is now an adult and is identified in court filings as Jane Doe 4 alleges that the plaintiff’s stepfather uploaded a photograph of the plaintiff taken in childhood to xAI’s Grok on or before 12 February 2026 and prompted Grok to generate about 7,000 AI-generated sexual images and videos of the plaintiff, and that the stepfather traded them online. The plaintiff joined a proposed class action against xAI in the Northern District of California through an amended complaint filed on 7 July 2026. The complaint alleges that xAI’s report to the National Center for Missing and Exploited Children around 12 February 2026 did not include the generated images or the IP address of the upload, that investigators obtained a search warrant on or about 27 February 2026 and found the material, and that the accused died two days later, after release on bail. The plaintiff reports severe distress including depression and suicidal thoughts and told the Washington Post about starting therapy. The complaint says the accused was charged with child exploitation offenses while the plaintiff told the Post that the accused was not charged with child pornography offenses. xAI did not respond to the Post and had not answered the complaint in court. The allegations have not been tested in court. The plaintiff and the accused are not named here, and the images are described only by kind.

Core concern High reported severity

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

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

2025Event location unknownGrok (reported)

Australian campaigner says harassers sent and posted AI-generated violent and sexual images of her with threats during 2025

Caitlin Roper, campaigns manager at the Australian group Collective Shout, told the New York Times (31 October 2025), Mamamia and AAP that from what the Times calls the summer of 2025 people sent and posted images and a video of her that she describes as AI-generated deepfakes, including violent images and images she says were undressed with Grok, X's AI feature, together with threats. The Times captioned them as AI-generated images; its article says the violent images were seemingly enabled by generative AI and that some harassers claimed to have used Grok to create images. Roper says the abuse was deeply traumatic, that for months she spent at least an hour each morning reporting, blocking and documenting it, and that police and the eSafety Commission gave little help. The Times reports that X told her some posts depicting her violent death did not breach its rules and temporarily locked her account after she posted examples. The senders are not identified, and no forensic examination of the images is reported.

Core concern Medium reported severity

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