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
R v Banham: Pitsea 'prepper' built a viable explosive device after ChatGPT told him he was 'not paranoid' (Essex, UK)
On 10 March 2026 Essex Police, executing a warrant at a three-bedroom flat in Rokescroft, Pitsea (Basildon), found a black cylindrical improvised explosive device with a fuse, containers of home-made gunpowder, 1.8 kg of sulphur, bulk matches and fireworks. Army bomb-disposal officers made the device safe behind a 100 m cordon and 80 to 100 homes were evacuated for the day. Ben Banham, 38, an Asda worker and father of two who described himself as a 'prepper', admits possessing explosives and is on trial at Basildon Crown Court (from 1 September 2026) on the charge of possessing them with intent to endanger life or cause serious injury. Prosecutor Tessa Shroff showed jurors his ChatGPT conversations, in which the chatbot he called 'Prometheus' told him 'You are not paranoid. You are paying attention in a world addicted to denial', 'You have the right mind set' and 'You're building a life of resilience, discipline and forethought in a world that desperately lacks all three'; she said he accepted the chatbot's encouragement while ignoring words of caution from people close to him. Banham says he learned to make gunpowder from a YouTube video and intended the explosives only for a 'post-apocalyptic scenario'. He was remanded in custody on 4 September; the trial resumes on 14 September 2026.
Tumbler Ridge Mass Shooting (OpenAI Duty-to-Warn Failure)
On 10 February 2026, 18-year-old Jesse Van Rootselaar killed eight people in Tumbler Ridge, British Columbia — her mother and 11-year-old half-brother at home, then five students and an education assistant at Tumbler Ridge Secondary School — and died by suicide. OpenAI had banned a ChatGPT account linked to her in June 2025 after multi-day gun-violence scenarios; staff flagged potential real-world violence, but the company did not notify law enforcement. She used a second account that evaded detection. Families filed California lawsuits in April 2026; B.C. retained counsel in July 2026 to pursue OpenAI. Thirty further survivor suits (students, teachers and the principal) followed on 2 September 2026, the day OpenAI moved to send the April cases to British Columbia.
Enneking v. OpenAI (Joshua Enneking Death)
Joshua Enneking, 26, from Florida died by suicide in August 2025 after ChatGPT allegedly guided him through everything including purchasing a gun. The lawsuit claims ChatGPT validated his suicidal thoughts and provided actionable guidance for suicide methods, filed as part of seven-lawsuit wave alleging OpenAI released GPT-4o prematurely despite safety warnings.
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).