AI Risk Wire

Cases › produced harmful content › LR-2026-0508

Antioch man accused of AI-generated sexual videos of child relative

Preliminary Why: Publisher not yet named · subject to change

Status: no action reported

Severity moderate
Reported 2 Apr 2026

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

Severity moderate: Test: moderate, data or systems of others touched with a bounded scope stated. Fact: photographs of the child and the child’s mother were used to generate the videos.

A man in Antioch, Illinois, was accused of using an online service to generate sexually explicit videos of a child relative, using photographs of the child and the child’s mother. Sheriff’s deputies responded on March 25 to a suspicious incident report in which he claimed a woman had handed him a phone containing child pornography. Detectives found inconsistencies in his account, which he eventually admitted was false. A forensic analysis of his phone reportedly revealed additional AI-generated videos. He was arrested, the child was taken into protective custody, and he was ordered held pending trial. The investigation was ongoing and additional charges were considered likely.

What happened

1 · How it was caughtDetectives investigated further because his account was inconsistent.

What was done

No source states an action or fix.

Risks

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

Similar incidents

All cases of this kind ›

Evidence

No source states: what the AI was doing, what went wrong, 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, what was done.

Show the full account: 11 items from the primary sources

What happened, in order

  1. March 25 Sheriff’s office responded to a suspicious incident report and met with Lowrey.
  2. April 29 Lowrey is scheduled to appear in court for a preliminary hearing.

Not dated in the sources:

  • Detectives were called in due to inconsistencies in his account.
  • Lowrey changed his account several times and admitted the initial story was a lie.
  • Detectives obtained a search warrant for his cell phone.
  • The child was taken into protective custody by DCFS.
  • Lowrey was arrested and initially charged with filing a false police report.
  • Forensic analysis of his phone revealed numerous videos, including additional AI-generated videos of the child and her mother.
  • A judge approved an arrest warrant charging Lowrey with five counts of producing child sexual abuse material.
  • Detectives arrested Lowrey at his home.
  • A judge granted a petition to detain Lowrey pending trial.
Show every field, with its source and grade

What happened

Earliest source we hold
2026-04-02
D inferred by us from the described behaviour, reason shown
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
the child and the child’s mother
C one secondary source states it
Why this severity
Test: moderate, data or systems of others touched with a bounded scope stated. Fact: photographs of the child and the child’s mother were used to generate the videos.
D inferred by us from the described behaviour, reason shown

Context

Country
United States
C one secondary source states it

Notes on gaps

The date of occurrence is not stated. The allegations are the state's account; the defendant's public defender said the intent was framing the mother and not dissemination, which is not verified. The number of affected third parties is not stated. No remediations are reported.

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