AIPolicyTracker

AI incident ·

Delhi Man Allegedly Used AI to Create and Circulate Obscene Images of College Acquaintance

2 news reports Synced from source · record last edited 9 Sep 2026

In brief

An AI system built by Synthetic media generation technology developers, Synthetic image generation technology developers and 1 other and deployed by Synthetic media creators, Keshav Bansal and 1 other allegedly harmed Women and girls, Women and 5 others.

Risk domain
Not classified
Occurred
Coverage
2 reportsSep 2026

What happened

Delhi police alleged that a man named Keshav Bansal used photographs from a college acquaintance's private social media account with AI image-generation and editing tools to create obscene morphed images and upload them to anonymous Discord servers. The woman reported fake accounts and threatening messages intended to humiliate and harass her. Police arrested Bansal and said the investigation was ongoing.

Laws that address this harm

No recorded instrument yet addresses this use case where it happened. See the open queue.

Matched from the record's risk domain and country to the instruments recorded here. A reviewer can correct the match in the repository (data/external/incident_overrides.yaml).

News reports (2)

Titles link to the original publisher; report text is not reproduced here.

  1. Resentment leads techie to circulate fake obscene images of woman online
    timesofindia.indiatimes.com · The Times of India

Who was involved

Alleged harmed party
Women and girls Women Victims of non-consensual deepfakes Victims of deepfake abuse Privacy Individuals subjected to sexual exploitation imagery Epistemic integrity

AI systems implicated

Synthetic media generation technologySynthetic image generation technologySocial media platformsInstagramDiscordDeepfake technology

Classification (MIT AI Risk Repository taxonomy)

Risk domain
—
Risk subdomain
—
Causal entity
—
Intent
—
Timing
—
Harm level
—
Sectors
—
Countries
—

Other incidents involving Synthetic media creators

Source record: incident #1683 on the AI Incident Database · all 2 reports