aceEmerging evidence
Published recordCrimeGeneral
More
Explaining peer-generated AI-CSAM: A criminological analysis of youth offending, gendered harm and technology-facilitated sexual abuse
- Truvace record
- TRV-2026-2516raw data (JSON)
- Version
- v2Revised
- First published
- Evidence type
- Commentary, opinion, or narrative review
- Sources
- 1 sourcePeer-reviewed
- sha256
- 0d0dc7224a1b…check it
Artificial intelligence has transformed the landscape of sexual harm, particularly towards women and girls, by enabling the rapid creation of synthetic hypersexualised material, including peer-generated modification images and deepfakes, falling under the category of child sexual abuse material (AI-CSAM). While research has focused primarily on adult offenders, far less attention has been given to the growing involvement of children and young people in producing AI-generated sexual imagery of peers. This review…
The problem
A literature review argues that AI tools now let children and young people quickly make synthetic sexual images and deepfakes of peers, mostly targeting women and girls, and that adult-focused research has left this youth offending understudied.
What this doesn’t fix
The work is a conceptual literature review that offers a theoretical framework and identifies gaps for future research rather than measuring how common peer-generated AI-CSAM is or testing whether the proposed model works.
Sources
1 on file- Criminology & Criminal Justicedoi:10.1177/17488958261467387
Cite this record
v2Truvace Impact Record TRV-2026-2516, v2: “Explaining peer-generated AI-CSAM: A criminological analysis of youth offending, gendered harm and technology-facilitated sexual abuse.” Truvace, 2026-11-12. /record/TRV-2026-2516 (accessed on the day you copy it). sha256 0d0dc7224a1bbc89…
Change history
2 versionsEvery change made to this record since it was first published, and why.
Filed as context: this is an argument or a review without a measured outcome, so it is not counted as a problem. The record's text is unchanged.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2516 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.