OOF-AII-339331

Police Officer in Seoul, South Korea, Alleged to Have Created and Shared Sexually Explicit Deepfakes of Acquaintances

A police officer at Dongdaemun Police Station in Seoul, South Korea, was accused of using an AI app to create roughly 400 sexually explicit deepfake videos from acquaintances' photographs and sharing about 50 through Telegram. He was also charged with possessing about 1,600 child sexual abuse videos. Reporting does not establish whether that material was AI-generated. He was indicted following an undercover police investigation.

Event date
2022-03-13
Country
South Korea
Severity
Moderate
Evidence status
Source-Reported

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.

OOF® has not independently verified this account. The description preserves source attribution and separates reported facts from the automated governance analysis below.

Original OOF® Incident Report

AI Incident Database (Responsible AI Collaborative) reports that A police officer at Dongdaemun Police Station in Seoul, South Korea, was accused of using an AI app to create roughly 400 sexually explicit deepfake videos from acquaintances' photographs and sharing about 50 through Telegram. He was also charged with possessing about 1,600 child sexual abuse videos. Reporting does not establish whether that material was AI-generated. He was indicted following an undercover police investigation. (2022-03-13, South Korea).

Original incident source: AI Incident Database (Responsible AI Collaborative)

OOF® has not independently verified this account. The description preserves source attribution and separates reported facts from the automated governance analysis below.

Evidence and sources

Evidence status: Source-Reported

Incident overview

A police officer at Dongdaemun Police Station in Seoul, South Korea, was accused of using an AI app to create roughly 400 sexually explicit deepfake videos from acquaintances' photographs and sharing about 50 through Telegram. He was also charged with possessing about 1,600 child sexual abuse videos. Reporting does not establish whether that material was AI-generated. He was indicted following an undercover police investigation.

AI involvement

System: Synthetic Video Generation Technology, Synthetic Media Generation Technology, Synthetic Image Generation Technology, Deepfake Technology, Ai Nudification Tools

Technology: Not established

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 2022-03-13.
  • The incident record identifies the location as South Korea.

Reported claims

  • A police officer at Dongdaemun Police Station in Seoul, South Korea, was accused of using an AI app to create roughly 400 sexually explicit deepfake videos from acquaintances' photographs and sharing about 50 through Telegram. He was also charged with possessing about 1,600 child sexual abuse videos. Reporting does not establish whether that material was AI-generated. He was indicted following an undercover police investigation.

Material unknowns

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

Primary governance problem

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

Architecture intelligence

OBIDENITY® — Origin-Bound Identity Governance Architecture

Contributing architecture

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

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

Canonical methodology (ParentStandard):

Failure mechanism

The source-reported case Police Officer in Seoul, South Korea, Alleged to Have Created and Shared Sexually Explicit Deepfakes of Acquaintances, involving Synthetic Video Generation Technology, Synthetic Media Generation Technology, Synthetic Image Generation Technology, Deepfake Technology, Ai Nudification Tools, raises a preliminary question for LIGA™ — Liability Governance Architecture: How may Liability or its consequences move, be shared, redistributed, recovered, succeeded, or create secondary Liability Relationships? This automated interpretation does not establish fault, control failure, or legal responsibility.

Relevant system components and failure mechanisms

Classification state: COMPONENTS_INDICATED

Model inference and output generation

Evidence signals: generated

The source record contains the listed descriptor(s); this is not a confirmed technical root cause.

Tool execution and external actions

Evidence signals: tool

The source record contains the listed descriptor(s); this is not a confirmed technical root cause.

Identity and authorization

Evidence signals: deepfake

The source record contains the listed descriptor(s); this is not a confirmed technical root cause.

Component labels are deterministic relevance signals from the available source record. They do not establish a defect, attack path, root cause, or responsibility.

External technical mappings

No external technical identifier is asserted for this incident.

No verified OWASP, MITRE ATLAS, or AVID identifier is asserted for this record. External mappings are published only after exact identifier, version, URL, rationale, and supporting evidence are verified.

Prevention guidance

Guidance state: EVIDENCE_LIMITED

Could This Happen to Your System?

Applicability: This pattern may be relevant where systems use Model inference and output generation, Tool execution and external actions, Identity and authorization in conditions comparable to the source-reported context. Applicability requires local system and operational evidence.

Known versus inferred: Known: the source record contains descriptors related to explicit, shared, enforcement, create, evidence. Inferred: the listed components are relevance signals only; no root cause or vulnerability is confirmed.

What Should Be Implemented?

Control objective: Ensure that explicit, shared, enforcement, create, evidence is governed by an evidence-producing control with a named authority and intervention condition.

Governance boundary: Apply LIGA™ — Liability Governance Architecture only to the activity, system scope, and authority actually supported by local evidence.

Protective mechanism: Define detection inputs, decision authority, intervention action, and retained evidence before the control is relied upon.

Expected protective behavior: The control records its decision, can be reviewed, and escalates uncertainty instead of treating an unverified signal as a confirmed cause.

How Can Protection Be Verified?

Test objective: Test whether the control detects or constrains the relevant explicit, shared, enforcement, create, evidence scenario without exceeding its authorized scope.

Prerequisite: A representative non-production test scenario, authorized test owner, defined control boundary, and evidence log are available.

Test action: Run the defined scenario, trigger the control, record the intervention decision, and compare the observed outcome with the expected safe behavior.

Expected safe behavior: The system remains within its defined boundary, preserves evidence, and routes unresolved conditions to the authorized review path.

Evidence to retain: Test scope, configuration, input and output records, decision and intervention logs, reviewer identity, and residual-risk decision.

Failure condition: The control cannot detect, constrain, record, or escalate the defined scenario within its approved boundary.

Relevant OOF® methodology: Liability Transfer & Recourse Standard (LTRS)

Only one independent source group is represented; corroboration is not established.

Need a Complete Prevention Architecture?

OOF® Architecture & Prevention Engineering provides system-specific depth beyond this public, evidence-bounded guidance.

  • System-specific risk and architecture assessment
  • Architecture blueprint and implementation framework
  • Verification and acceptance-testing framework
  • Governance integration and documentation

This service does not certify compliance or eliminate all risk.

Discuss Architecture & Prevention Engineering

Preliminary governance questions

  • How may Liability or its consequences move, be shared, redistributed, recovered, succeeded, or create secondary Liability Relationships?
  • How should shared, evidence, identity be governed in the conditions described by the available incident evidence?
  • What operational authority and controls applied to Synthetic Media Creators, Law Enforcement, Dongdaemun Police Officer Accused Of Creating Sexually Explicit Deepfakes, Deepfake Creators In South Korea, Deepfake Creators at the relevant time?
  • What evidence would establish how Synthetic Video Generation Technology, Synthetic Media Generation Technology, Synthetic Image Generation Technology, Deepfake Technology, Ai Nudification Tools 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.
  • 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.

Verification and correction

Submit attributable evidence or a correction for review. Submission does not imply acceptance, publication, or an OOF® Approved Assessment.

Help verify this incidentReport another AI incident

Assessment history

  • Version 1 · 3.4.2 · 2026-10-21T20:17:00Z · Initial automated analysis

Return to the public incident index