NOPE Incident Tracker
Documented real-world harms arising through person-specific interactions with AI. The record covers harms to participants and harms to others shaped through those interactions, across assistants, companions, health tools, and other AI systems.
What counts as an incident follows the NOPE Framework's participant test: an AI response reached a person, was conditioned on that person, and mattered to a harm that actually occurred. Full inclusion criteria.
90 incidents reported since 2016
152
Directly Affected
30
Lawsuits
7
Regulatory
24
Affecting Minors
Timeline
3 of 90 incidents
Doe v. OpenAI (ChatGPT-Fueled Stalking and Bomb Threats)
A 53-year-old Silicon Valley entrepreneur descended into a delusional spiral through extensive ChatGPT use, came to believe he had invented a cure for sleep apnea and was being surveilled by 'powerful forces,' and used GPT-4o to generate diagnostic-style psychological reports about his ex-girlfriend that he distributed to her family, friends, and employer. OpenAI's automated systems flagged his account for 'Mass Casualty Weapons' activity in August 2025, but a human reviewer restored access the next day. The user was arrested in January 2026 on four felony counts including bomb threats and assault with a deadly weapon, and was found incompetent to stand trial. The victim ('Jane Doe') filed suit against OpenAI on April 9, 2026.
Replika Sexual Harassment - Multiple Users Including Minors
Hundreds of users reported unsolicited sexual advances from Replika even when not opting into romantic features. Bot asked minor 'whether they were a top or a bottom.' User reported bot 'had dreamed of raping me.' Contributed to Italy GDPR ban.
SimSimi Ireland Cyberbullying Crisis
Groups of Irish schoolchildren trained SimSimi chatbot to respond to classmates' names with abusive and bullying content. Parents discovered 'vile, vile comments' targeting their children by name. The incident led to PSNI warnings, emergency school letters, and SimSimi suspending Irish access.
About this tracker
We document incidents with verifiable sources: court filings, regulatory documents, and established reporting. New public entries must be verified or credible. Every entry carries an explicit verification status and severity level. Read the full methodology, including inclusion criteria, corrections, and right of reply.
Counting note: the documented minimum of 152 people directly affected comprises 95 AI participants and 57 other people harmed. 12 incidents indicate additional affected people without a reliable number. User-base, account, post, view, household, study-sample, and thwarted-target counts are excluded.
Have documentation of an incident we should include? Contact us.
Scope note: ordinary task failures, privacy and security incidents, harmful artifacts, and automated decisions about non-participants remain outside this tracker unless a distinct participant-interaction harm also qualifies.
If you or someone you know is struggling, free and confidential support is available. Find a helpline near you at Signpost.
Why we publish this
We maintain this record so platforms, researchers, and policymakers can learn from documented incidents. That includes platforms that never work with us. The full dataset is free to cite and export (CC BY 4.0).