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
3
Countries with reported events
2
Located 2 of 3 cases · 1 unknown
Languages in checked sources
3
Recorded for 3 of 3 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 HighMediumLow
More filters: AI relation, use, setting, sources and responses
Clear filters

3 of 1099 published cases

13 Sept 2026JapanUnidentified website-generation tool

Japan: police say two teenagers used generative AI to build a fake payment-service site that took women's details, later used to pay for a hotel and consoles

Shiga prefectural police sent two teenagers' cases to prosecutors on 27 October 2026 on suspicion of violating Japan's unauthorised computer access law. According to the police announcement as reported by the Yomiuri Shimbun and Asahi Broadcasting (ABC), on 13 September 2026 the two, in Tokyo, sent two women the URL of a site made to look like a real payment service, told them they could receive money, and had them enter details such as email addresses and phone numbers. Police say the two used generative AI to make the phishing site, and the Yomiuri reports that one of them, who is believed to have used generative AI to make the fake site, said he did not have the skill to build a site without AI. The same day, police say, they logged into a travel-booking site with one woman's details and paid a Tokyo hotel bill of 182,830 yen; they were later re-arrested over three portable game consoles bought with another woman's account. Police believe they took about 50 people's information, including from other payment services, and charged about 5 million yen. Both admitted the allegations, according to the police. They are not named here.

Core concern Medium reported severity Criminal Charges

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

Sept 2026Event location unknownGoogle AI Mode

Investigator says Gemini told a victim a fake TRON energy-rental site was safe; a screenshot he posted shows Google AI Mode calling it the official domain

On 4 October 2026 a crypto investigator who posts on X as JP (@rugpullfinder) said a fake TRON energy-rental site, tronify.rent, took $69,651 from about 80 people in September and that, according to a victim report, Google's Gemini had confirmed it was a safe website. His post carries two screenshots. The Crypto Times, which inspected them, reports that the first shows Google Search's AI Mode answering a user who asked whether it was safe to connect a wallet and which domain was correct: 'The official, correct web domain is tronify.rent', supported by a statement that Trust Wallet had natively integrated Tronify. In the same answer, under a heading on avoiding scams, it tells users never to approve unlimited token allowances. The Crypto Times reports that Trust Wallet's October 2025 announcement of the integration does not name tronify.rent and that a December 2024 Trust Wallet post links to Tronify's market at tronify.io. The second screenshot shows Trust Wallet notifications dated Monday, 28 September: an unlimited USDT approval to an address on the investigator's list, then 1,419.699184 USDT sent to another listed address. The Crypto Times has not verified the loss total or the victim count. No inspected source publishes the victim's own account or says the screenshots come from that victim.

Core concern Low reported severity Media Coverage

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

12 Jun 2026RussiaChatGPT

Russia: a crypto investor lost about $2.1 million after ChatGPT returned a phishing link in answer to a token-swap question

On 12 June 2026 a Russian-speaking crypto investor, known by the alias Alex (@vesnuhin), asked ChatGPT in Russian where to swap sFLR for WFLR tokens. ChatGPT's reply included a link to sceptre.network, a phishing clone of the legitimate sceptre.fi. He connected his wallet and signed an unlimited-approval transaction; within seconds about 1.9 million FXRP, worth roughly $2.1 million (about 180 million rubles), were drained. A blockchain analyst traced the theft, and reported that the phishing link appeared only in Russian-language answers. Russia's Interior Ministry (MVD) later confirmed the loss.

Core concern High reported severity Investigation Opened

AI involvement supported · Causal attribution supported · 4 sources, 2 underlying accounts · Added 17/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.