OOF-AII-031813

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

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.

Event date
2026-09-09
Country
Location not specified
Severity
High
Evidence state
Single-source

Assessment status

Generated from available public incident evidence using OOF® governance methodology. It is not an official investigation, legal determination, regulatory finding, certification, or OOF® Approved Assessment.

View source record from AI Incident Database (Responsible AI Collaborative)

Assessment confidence dimensions

Source corroboration
Single-source

Measures source-group corroboration only; it does not establish factual truth.

Extraction completeness
Moderate

Measures populated source fields after deterministic normalization; it does not measure correctness.

Methodological assignment confidence
High

Measures automated assignment support; substantive correctness requires authorized human review.

Known facts from the incident record

  • The incident record identifies the event date as 2026-09-09.

Reported claims

  • 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.

Material unknowns

  • Independent corroboration is not established in the available incident record.

Primary governance problem

The incident appears to expose a governance problem involving evidence, identity, origin. Available reporting supports preliminary methodological interpretation, not a finding of fault or non-compliance.

Architecture intelligence

OBIDENITY® — Origin-Bound Identity Governance Architecture

Primary architecture

The reported evidence, identity, origin concern falls within the governed questions represented by OBIDENITY® — Origin-Bound Identity Governance Architecture.

Governance focus: How should evidence, identity, origin be governed in the conditions described by the available incident evidence?

Canonical methodology (ParentStandard):

LIGA™ — Liability Governance Architecture

Contributing architecture

The reported create, evidence, them concern falls within the governed questions represented by LIGA™ — Liability Governance Architecture.

Governance focus: How should create, evidence, them be governed in the conditions described by the available incident evidence?

Deeper methodology is withheld because the available evidence does not justify a Parent Standard or Core Module.

Preliminary governance questions

  • How should evidence, identity, origin be governed in the conditions described by the available incident evidence?
  • How should create, evidence, them be governed in the conditions described by the available incident evidence?
  • What operational authority and controls applied to Keshav Bansal, Synthetic Media Creators, Deepfake Creators at the relevant time?
  • What evidence would establish how Synthetic Image Generation Technology, Synthetic Media Generation Technology, Deepfake Technology, Discord, Instagram, Social Media Platforms produced or enabled the reported outcome?
  • What additional independent evidence is required to resolve the material evidence gaps?

Evidence gaps and limitations

  • Only one independent source group is represented; corroboration is not established.
  • Country could not be resolved from the available evidence.
  • AI technology is not specified in the source record.
  • industry is not specified in the source record.
  • AI system type is not specified in the source record.

Return to the public incident index