Artificial Intelligence Policy Tracker

AI incident ·

Teenager in Quilmes, Argentina, Reportedly Consulted ChatGPT While Planning School Shooting Against Classmates

4 news reports Synced from source · record last edited 12 Sep 2026
On this page 7 sections

In brief

An AI system built by OpenAI, Large language model developers and 1 other and deployed by Unnamed adolescent boy in Quilmes, Argentina and 8 others allegedly harmed Victims of school violence planners and assailants, Teachers and 6 others.

Risk domain
Not classified
Occurred
Coverage
4 reportsSep 2026

What happened

Argentine authorities reported that a 15-year-old in Quilmes allegedly discussed a planned school shooting with ChatGPT, including tactical preparations, before an FBI alert prompted an investigation by the Argentine Federal Police. Police later seized phones and tactical clothing; no firearms or ammunition were reported. Public reporting does not establish what ChatGPT answered or whether it materially assisted the alleged plan.

Laws on record for this risk area

No instrument on record yet covers this risk area where it happened. See the open queue.

Matched from the record's risk category and country to the instruments in effect recorded here: a law listed covers the area, which is not a finding that it applies to this incident. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (4)

Titles link to the original publisher; report text is not reproduced here.

Who was involved

Alleged harmed party
Victims of school violence planners and assailants Teachers Students Minors Educators Educational communities Classmates of unnamed adolescent boy in Quilmes, Argentina

AI systems implicated

OpenAI large language modelsLarge language modelsChatGPTChatbots

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Linked by editors or by text similarity in the source dataset.

Source record: incident #1688 on the AI Incident Database · all 4 reports