AI Risk Wire

Cases › produced harmful content › LR-2026-0692

Kane County, Illinois man charged over AI-generated child sex abuse images

Preliminary Why: 1 report: CBS News · subject to change · 1 independent report

Status: no action reported

Severity moderate
Reported 20 Aug 2026

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

Severity moderate: test met: images of others (real children) were touched, with a bounded scope stated (photographs taken at two named locations, Lord of Life Church and Thompson Middle School).

Prosecutors allege that a man in Kane County, Illinois used AI apps available to the public to alter photographs of real children and to generate sexually explicit images of children from scratch. The alleged activity ran between November 2025 and May 2026, and the photographs were reportedly taken at a church and a middle school. A CyberTip to the National Center for Missing and Exploited Children brought the man to the attention of law enforcement, and a three-month investigation followed. Charges were filed August 12 and he was taken into custody the next day. A judge ordered him detained pending the case. Prosecutors do not believe any of the material was shared online.

What happened

1 · What it was doingMan allegedly took real photos of children and used AI apps to make them sexually explicit.
2 · What went wrongProsecutors allege photos were taken at a church and a middle school, then altered or generated into abuse images with AI.
3 · How it was caughtA CyberTip to the National Center for Missing and Exploited Children led police to the man.

What was done

No source states an action or fix.

Risks

Privacy harm to a person
Primary41 incidents

Read from the sources; not yet reviewed by a person.

Controls

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

Application

Data minimisation · Sensitive-data checks on outbound data · Human approval for high-impact actions · Output filtering and redaction · People told they are dealing with AI · Risk assessment per deployment

Infrastructure / target

Bot and scraping defences

Evidence

No source states: 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 was done.

Show the full account: 7 items from the primary sources

What happened, in order

  1. Nov. 13, 2025 to May 17, 2026 Alleged period of AI image production.
  2. Aug. 12 (charges filed); Aug. 13 (custody) Charges filed and man taken into custody.
  3. Aug. 14 Pretrial detention hearing.
  4. Thursday, Aug. 20 Next court appearance scheduled (per Patch).

Not dated in the sources:

  • Investigation began after a tip from the Internet Crimes Against Children Task Force.
  • CyberTip to NCMEC brought the man to law enforcement's attention.
  • Three-month investigation by the Kane County Child Exploitation Unit.
Show every field, with its source and grade

What happened

Earliest source we hold
2026-08-20
D inferred by us from the described behaviour, reason shown
What set it off
misused by a person
C one secondary source states it
Who caught it
an outside party
C one secondary source states it
What went wrong
produced harmful content
C one secondary source states it
primary risk
RK15
D inferred by us from the described behaviour, reason shown

Impact

Severity
moderate
D inferred by us from the described behaviour, reason shown
Who was affected
Real children photographed at Lord of Life Church in Elburn and Thompson Middle School in St. Charles, some as young as 11, whose images were allegedly altered or generated with AI.
C one secondary source states it
Why this severity
test met: images of others (real children) were touched, with a bounded scope stated (photographs taken at two named locations, Lord of Life Church and Thompson Middle School).
D inferred by us from the described behaviour, reason shown

Notes on gaps

Sources describe prosecutors' allegations only; no conviction is stated. No remediation is reported.

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