IN THIS BREAKDOWN · 10 SECTIONS
You can read 17% of this breakdown.
The paper in one minute
If a training dataset grows enormously while the number of malicious examples stays fixed, their percentage becomes tiny. It is tempting to conclude that their effect must also disappear. This paper tests that assumption rather than treating the fraction as a sufficient risk measure.
The authors train models at several scales while controlling the absolute number of poisoned documents. In the main experiments, a few hundred documents are sufficient to induce a trigger-dependent degradation in generation across the tested model sizes. Larger amounts of clean data do not reliably dilute that learned behavior away.
The headline needs its scope. The full-pretraining experiments concern a particular denial-of-service backdoor and models up to 13 billion parameters. Other experiments examine language switching and fine-tuning. The study does not prove that the same document count can implant any behavior in every frontier model.
For an FDE, the lasting lesson is to track data origin, absolute exposure and conditional behavior. A small contamination percentage and an unchanged average benchmark score are both weak reasons to dismiss a possible training-data problem.
Research notes: the problem, approach and results
sufficient in the reported main denial-of-service experiments
model parameter range in full-pretraining experiments
24 pretraining configurations across three seeds
Poisoning risk can be understated when measured only as a percentage of a growing dataset.
Hold the absolute number of malicious examples fixed while varying model and clean-data scale.
The tested backdoor behaviors depend strongly on absolute exposure, with important limits on generalization.
Why it matters to an FDE
An enterprise team may fine-tune on support transcripts, contractor annotations or harvested examples. A quality dashboard can report a very low suspicious-record fraction while overlooking repeated examples from one compromised source. The relevant exposure includes how often those records are actually sampled during training.
This paper concerns changes learned into model weights. It is different from prompt injection, where untrusted material influences a running model through its input. Both can affect agents, but the evidence to collect and the remediation steps differ.
Use audit trails to connect a model version to its dataset and training configuration. Preserve a way to identify affected runs and roll back. When assessing a vendor model, ask about data controls and behavioral evaluation without pretending that a downstream application can inspect or certify an unavailable training corpus.
Understand the mechanism. Try it on a real problem.
Unlock this breakdown and 199 more papers.
Premium opens every paper in full, plus every answer, concept, course and guide on the site. One payment for six months of access.
6 months · One payment · No auto-renewal
- ◇1 architecture diagram
- </>2 runnable code blocks
- ▦3 results tables
- 03Key takeaways
Evaluate poisoning evidence without generalizing a narrow attack result too far
Free account - 04How it works
Follow fixed-count experiments and distinguish full pretraining from continuation studies
Premium - 05The numbers that matter
Read document counts and model scales without treating them as universal thresholds
Premium - 06Try it yourself
Calculate why a clean random audit can miss a small fixed set of problematic records
Premium - 07Where it breaks
Recognize limits on post-training persistence, model scale and ingestion assumptions
Premium - 08Using it on a deployment
Strengthen data lineage and release checks while preserving a clear incident-response path
Premium - 09Interview angles
Explain why low contamination percentages and normal benchmark scores can both be misleading
Premium - 10Read next
Distinguish training-data compromise from reward-driven behavior and runtime prompt injection
Premium
