Cases › made things up › LR-2026-0536
EY withdraws report over AI hallucination errors, fake data and citations
Preliminary Why: Publisher not yet named · subject to change
Status: fix reported
No source states: loss or records, developer and model, agent tool, could do, deployer.
Ernst & Young (EY) published a study on loyalty rewards programmes, written by its consultants in Canada to market their cybersecurity business. The company said the study was not connected to any EY client project. Researchers at the AI detection startup GPTZero found that the report contained made-up data points, misattributed citations, and a cited McKinsey report that does not exist. EY removed the report from its website and said it was reviewing the circumstances that led to its publication. EY said it takes the accuracy of its published content seriously and has an organisation-wide commitment to the responsible use of AI.
What happened
What was done
“Report removed from the EY website; the firm is reviewing the circumstances that led to its publication”
Risks
Read from the sources; not yet reviewed by a person.
Controls
Not yet read for controls. Controls that mitigate the primary risk:
ApplicationGrounding and fact checks · Human approval for high-impact actions · Output filtering and redaction · People told they are dealing with AI
Evidence
No source states: what it reached or did, when it happened, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.
Show the full account: 3 items from the primary sources
What happened, in order
- Thursday, May 14 GPTZero researchers published a blog post reporting the fabricated content.
Not dated in the sources:
- EY consultants published the study.
- EY removed the report from its website in response and said it was reviewing the circumstances that led to its publication.
Show every field, with its source and grade
What happened
Impact
Context
Notes on gaps
The Deloitte and Sullivan & Cromwell cases are separate incidents and were excluded.
LR-2026-0536 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON