TRV-2026-1672Certified recordPeer-reviewed

REGULATING DEEPFAKES IN NIGERIA: ASSESSING THE ADEQUACY OF THE EXISTING CYBERCRIME FRAMEWORK

Generative artificial intelligence now enables the cheap fabrication of audio, images and videos of real people. Nigeria has been the scene of a range of such abuse, from a cloned-voice clip preceding the 2023 elections to deepfakes of the President and of Peter Obi from 2024 to 2026. This article examines the adequacy of Nigeria’s cybercrime law to regulate deepfakes, based on four stages of their life: acquisition, synthesis, dissemination and consequence and four criteria of evaluation: rule clarity, institut…

Policy · Problem Space — documented harm · certified 2026-10-17 · v1 · article view · machine-readable

Current reading — problem

Nigeria's cybercrime framework offers no definition of synthetic media, no offence of non-consensual synthesis, no takedown duty and no rules for authenticating electronic evidence, leaving deepfake victims with limited protection.

What this doesn’t fix

The assessment is a qualitative doctrinal analysis of legal texts, and coverage of sexual deepfakes is described only as arguable, so the conclusions rest on interpretation rather than measured enforcement outcomes.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1672, v1: “REGULATING DEEPFAKES IN NIGERIA: ASSESSING THE ADEQUACY OF THE EXISTING CYBERCRIME FRAMEWORK.” Truvace, 2026-10-17. /record/TRV-2026-1672 (accessed at citation time). sha256 886892939865ce4b…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1886892939865…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1672 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.