AIWiki
Malaysia
Back to all articles
AI Foundationsevaluationbenchmarksdata leakage

Data Contamination

4 min readUpdated October 2026
Data Contamination
Type
Evaluation methodology problem
Also known as
Benchmark contamination, data leakage
First major concern
GPT-3 era, 2020
Typical detection
n-gram overlap, membership tests
Impact
Inflated benchmark scores, invalid model comparisons
Related
AI benchmarking, memorisation, overfitting
Data contamination occurs when examples from an evaluation benchmark appear — directly or in paraphrased form — in the data used to train the model being evaluated. Formally, if D_train is the training set and D_test the test set, contamination is the condition D_train ∩ D_test ≠ ∅. The result is "training on the test set": a model can score well by recalling familiar material rather than demonstrating genuine generalisation, inflating benchmark results and distorting comparisons between models.[1]

Background

Contamination has been a known risk since the earliest days of machine learning, but it became acute with large language models. Frontier models are trained on web-scraped corpora of trillions of tokens, and public benchmark datasets — GLUE, MMLU, HellaSwag, HumanEval, GSM8K — are widely mirrored across repositories, forums, blogs and derivative datasets. Filtering every occurrence is practically impossible at that scale: analysis of pretraining corpora found 12.2% of HumanEval samples present in The Pile and 18.9% in The Stack, and GPT-3's own evaluation flagged over 90% of examples in some benchmarks as contaminated.[2][4]

The problem is not limited to accidental overlap. A survey of contamination research identifies leakage during fine-tuning, contamination introduced through synthetic training data, and indirect post-deployment leakage through user interactions — as well as deliberate benchmark gaming.[1]

Key Concepts

  • Contamination vs memorisation. Memorisation asks whether a model can reproduce training data verbatim (a privacy concern); contamination is an evaluation question — whether prior exposure makes the score an invalid measure of generalisation. A model need not recite the test data for contamination to matter.[3]
  • Detection methods. The common approach is n-gram overlap analysis: comparing benchmark items against the pretraining corpus using matched substrings. Research shows smaller n and single-occurrence thresholds catch far more contamination than coarser settings, and that considering the longest contaminated substring works better than unioning all matches.[4]
  • Severity. Detected contamination levels have reached up to 45% on commonly used benchmarks in some audits, with multilingual benchmarks showing figures as high as 91.8%; Llama 2 showed over 16% contamination in the MMLU suite despite deliberate filtering.[5]
  • Mitigation. Decontamination filtering (n-gram, hash and embedding-based), private held-out test sets, dynamically refreshed benchmarks, and — more recently — proposals for contamination-resistant datasets released only in forms usable for inference but not for training.[5]

Why It Matters for AI

Benchmarks are the market signal of the AI industry: leaderboard positions drive funding, enterprise purchases and research prestige. When scores partly measure recall rather than capability, those signals decay. Studies show contamination can add an estimated 15–25 points to headline scores on benchmarks like HumanEval and BBH for some models.[4] A clean, non-public mirror of GSM8K lowered accuracy by up to 13% on popular model families.[5] For the field as a whole, unchecked contamination shortens the useful lifespan of every public benchmark and weakens claims of model progress.

>Key Takeaways

  • Data contamination is the overlap of training and evaluation data; it makes benchmark scores measures of recall as well as capability.[1]
  • Web-scale pretraining makes complete decontamination impractical — contamination is widespread, not rare.[2]
  • It is distinct from memorisation: it corrupts evaluation validity even when no verbatim reproduction is observed.[3]
  • Detection relies mainly on n-gram overlap tests; mitigation uses filtering, held-out sets, and refreshed or contamination-resistant benchmarks.[4][5]
  • For Malaysian buyers and evaluators of AI systems, contamination literacy means reading leaderboard claims — and vendor benchmarks — with appropriate scepticism.

See Also

References

🇲🇾Malaysian Context

🇲🇾 Relevance to Malaysia: Malaysian organisations evaluating AI vendors — banks running procurement through RFPs, universities benchmarking open-weight models, and agencies assessing National AI Action Plan deliverables — increasingly rely on published leaderboards. Understanding contamination is essential to reading those numbers honestly: a vendor's "state-of-the-art" score may reflect benchmark recall rather than superior performance on Malaysian English, Malay-language, or domain-specific tasks.

This matters most where AI outputs carry consequences: PDPA-governed decisions in banking and insurance, AI-assisted legal and public-sector tooling, and education assessments. Local researchers contribute to the mitigation agenda too — contamination-resistant evaluation is an active area where Malaysian computer science programmes can participate without needing frontier-scale training compute. MDEC-aligned AI adoption guidance and AI literacy programmes benefit from treating benchmark claims with the same scepticism the methodology demands.

References

  1. ↑Sainz, O. et al. "A Survey on Data Contamination for Large Language Models." arXiv:2502.14425, 2025 - https://arxiv.org/html/2502.14425
  2. ↑Riddell, A. et al. "On Leakage of Code Generation Evaluation Datasets." arXiv:2407.07565, 2024 - https://arxiv.org/html/2407.07565
  3. ↑Xu, R. et al. "When Large Language Models Know the Table: A Framework for Assessing Data Contamination in Tabular Datasets." arXiv:2510.20351, 2025 - https://arxiv.org/html/2510.20351
  4. ↑Golchin, S. et al. "Evaluation data contamination in LLMs: how do we measure it and (when) does it matter?" arXiv:2411.03923, 2024 - https://arxiv.org/html/2411.03923v1
  5. ↑"LLM Benchmark Datasets Should Be Contamination-Resistant." arXiv:2605.19999, 2026 - https://arxiv.org/html/2605.19999