TRV-2026-1300Certified recordPeer-reviewed

Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation

Abstract The rapid advancement of generative artificial intelligence (AI) has introduced both opportunities and challenges in the fight against misinformation. This scoping review synthesizes recent empirical studies to explore the dual role of generative AI—particularly large language models (LLMs)—in the generation, detection, mitigation, and impact of misinformation. Analyzing 24 empirical studies, our review suggests that LLMs can generate highly convincing misinformation, often exploiting cognitive biases a…

Policy · The Trace — both readings · certified 2026-10-06 · v1 · article view · machine-readable

Current reading — gain

LLMs demonstrated capacity to detect false claims and increase users' resistance to misinformation, with personalized corrections showing effectiveness.

Current reading — problem

LLMs can generate highly convincing misinformation that exploits audience biases, and exposure was found to reduce trust and influence decision-making.

What this doesn’t fix

Mitigation evidence is mixed and safeguards are not consistently applied, and the field lacks standardized evaluation metrics.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1300, v1: “Generative AI and misinformation: a scoping review of the role of generative AI in the generation, detection, mitigation, and impact of misinformation.” Truvace, 2026-10-06. /record/TRV-2026-1300 (accessed at citation time). sha256 3b2cb67651379cbe…

Calibration history

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

  1. Certifiedv13b2cb6765137…

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