AI Risk Wire

Cases › produced harmful content › LR-2026-0507

Nebraska middle school teacher accused of generating AI child abuse images

Preliminary Why: Publisher not yet named · subject to change

Status: action reported, no fix

Severity minor
Reported 23 Apr 2026
Industry education

No source states: loss or records, developer and model, agent tool, could do, deployer.

Severity minor: Test: minor (contained to one individual's account, no third party touched). Fact: NSP said it did not believe any of the teacher's students were victims in the case.

A middle school science teacher in Omaha, Nebraska, was accused of using artificial intelligence to generate child sexual abuse images on a Google account. According to court documents, Google reported a tip in February 2026 about 423 uploaded media files, and investigators later traced the associated IP address to the teacher. Prosecutors said 104 files were consistent with child sexual assault material. The teacher was arrested and charged with possession and distribution of child pornography, and his bail was set at $1 million. Authorities said they did not believe any students were victims. The case is believed to be among the first charged under a Nebraska law that took effect in September and makes AI-generated child pornography illegal. The investigation was ongoing at the time of reporting.

What happened

1 · What went wrongGoogle reported a tip about uploaded media files to the National Center for Missing and Exploited Children.
2 · How it was caughtInvestigators subpoenaed an internet provider for the IP address and identified the teacher as suspect.

What was done

The teacher was arrested at his home and charged with possession and distribution of child pornography.

Risks

Harmful content and jailbreaks
Primary84 incidents
Rising: 6 vs 3.8 a week

Sorted by rule from the case's fields; not yet read from the sources.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Model

Safety training and refusal · Content safety classifiers · Abuse monitoring and account enforcement · Outside red-teaming

Application

Output filtering and redaction

Evidence

No source states: what the AI was doing, what it reached or did, when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.

Show the full account: 3 items from the primary sources

What happened, in order

  1. 2026-02-23 Google reported a tip about 423 uploaded media files; the case was initiated.

Not dated in the sources:

  • Investigators identified the teacher as suspect after a subpoena for the IP address.
  • The teacher was arrested after a warrant was served at his home.
Show every field, with its source and grade

What happened

Earliest source we hold
2026-04-23
D inferred by us from the described behaviour, reason shown
Who caught it
an outside party
C one secondary source states it
What went wrong
produced harmful content
D inferred by us from the described behaviour, reason shown

Impact

Severity
minor
D inferred by us from the described behaviour, reason shown
Why this severity
Test: minor (contained to one individual's account, no third party touched). Fact: NSP said it did not believe any of the teacher's students were victims in the case.
D inferred by us from the described behaviour, reason shown

Context

Industry
education
C one secondary source states it

Notes on gaps

The arrest is dated only as Wednesday and the court appearance as Thursday; I took the disclosure date as the 2026-04-23 Thursday of the WOWT report, which is my inference from the article date. The risk RK12 is my mapping of the generated content to harmful content, not a stated policy breach.

LR-2026-0507 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON