55/100

Moderate evidence

ProblemPublished recordCrimeProblem Space

Reports of AI-related child sexual abuse material rise 8,400% in two years, data shows

Truvace record
TRV-2026-2957raw data (JSON)
Version
v1Published
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
3025ebd1648d…check it

Reports of artificial intelligence being used to sexually exploit children have risen by more than 8,400% in two years, research has found. A report by the Edinburgh-based Childlight – Global Child Safety Institute says AI-related child abuse material, including deepfakes using “nudify apps”, had risen from about 4,700 in 2023 to more than 400,000 in 2025. The images, although fake, can be used to blackmail children to demand money or more images. The research examined reports of material by tech companies to th…

The problem

A Childlight analysis of tech company reports to the US National Center for Missing and Exploited Children found AI-related child abuse material reports rose from about 4,700 in 2023 to more than 400,000 in 2025, an increase of more than 8,400%.

What this doesn’t fix

The figures count reports to a clearinghouse, and Childlight's Prof Debi Fry said improved detection and reporting may explain some of the increase.

Sources

1 on file
  1. The Guardiantheguardian.com
    Journalism2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2957, v1: “Reports of AI-related child sexual abuse material rise 8,400% in two years, data shows.” Truvace, 2026-11-16. /record/TRV-2026-2957 (accessed on the day you copy it). sha256 3025ebd1648de135…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv13025ebd1648d…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2957 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.