Claude Code Antifraud: Kolmogorov–Smirnov and the Not-So-Childish Anomalies in a Children's Olympiad

## Introduction In June 2026, the AI community witnessed a curious and revealing incident that highlights both the power and the peril of large language models in competitive programming. The story revolves around a children's programming Olympiad where participants, as young as 11–13 years old, were expected to solve algorithmic problems of moderate difficulty. The results, however, showed a statistical anomaly so stark that it prompted an investigation using methods borrowed from high-energy physics and econometrics: the Kolmogorov–Smirnov test. The tool at the center of this controversy is Claude Code — an AI-powered coding assistant developed by Anthropic. The incident, documented by a Russian-language AI community on Habr, demonstrates how LLM-generated code can be identified by its distinctive statistical fingerprint, even when the authorship is masked. This article unpacks the technical details of the detection methodology, the ethical implications, and what this means for the future of AI-assisted education. ## The Problem: When Children Code Like Senior Engineers A typical children's programming Olympiad features tasks such as: - Finding the shortest path in a grid (BFS/DFS) - Dynamic programming on small arrays - Basic string manipulation with prefix functions The expected solution style is naïve, often O(n²) or O(n³), with abundant comments, simple variable names, and occasional logical errors. In the 2026 edition of a major Russian-language children's Olympiad, a small subset of submissions stood out: they were flawless, used advanced data structures (Fenwick trees, segment trees with lazy propagation), and exhibited near-identical coding patterns — despite being submitted under different usernames. ## The Detection Methodology: Kolmogorov–Smirnov in Action The Kolmogorov–Smirnov (K-S) test is a non-parametric statistical test used to compare two empirical distributions. In this context, the test was applied to the distribution of code metrics such as: - **Token frequency distribution**: How often specific keywords (e.g., `for`, `while`, `if`, `else`, `return`) appear per 100 lines of code. - **Indentation style**: The distribution of whitespace, tabs, and newline patterns. - **Variable naming conventions**: The ratio of single-letter variables to descriptive names, and the entropy of identifier lengths. - **Comment density**: Number and placement of comments relative to code blocks. The investigators compiled a reference distribution from known human-written solutions from previous Olympiads (n=1,200 submissions) and a reference distribution from Claude Code-generated solutions (n=500 submissions, generated by prompting Claude with the same problem statements). | Metric | Human Submissions | Claude Code Submissions | K-S Statistic (D) | p-value | |--------|------------------|------------------------|-------------------|---------| | Token frequency (keywords) | Normal distribution μ=12.3, σ=3.1 | Normal distribution μ=9.8, σ=0.7 | 0.82 | <0.001 | | Variable name entropy | 3.4 bits | 1.2 bits | 0.91 | <0.001 | | Comment density (%) | 8.2% ± 4.1% | 2.1% ± 0.3% | 0.78 | <0.001 | | Indentation consistency | 0.72 (Gini coefficient) | 0.98 (Gini coefficient) | 0.85 | <0.001 | The K-S test revealed that the suspicious submissions had a D statistic exceeding 0.8 for nearly all metrics, with p-values far below 0.001 — indicating that the probability of these submissions being drawn from the same distribution as human submissions is effectively zero. ## Why Claude Code Leaves a Fingerprint Large language models like Claude Code are trained on vast corpora of code from GitHub, Stack Overflow, and other public sources. However, they exhibit several systematic biases: 1. **Low variance**: LLMs tend to generate solutions that are statistically average — they avoid extreme outliers in code length, complexity, or stylistic choices. Human programmers, especially children, show high variance. 2. **Consistent indentation**: Claude Code almost always uses 2-space indentation (its default), while human submissions show a mix of 2-space, 4-space, and tab-based indentation. 3. **Predictable variable names**: The model prefers generic names like `i`, `j`, `k`, `arr`, `temp`, `res`. Children often use more descriptive (if misspelled) names like `counter`, `biggestNumber`, `myArray`. 4. **No logical errors**: Even the best human coders in a timed competition make off-by-one errors, missing edge cases, or inefficient loops. Claude Code rarely does. ## The Broader Implications for AI-Assisted Education This incident is not about punishment — it's about understanding. The detection of AI-generated code in a children's Olympiad raises several critical questions: - **Fairness**: If some participants use Claude Code while others solve problems manually, the competition becomes meaningless. The organizers are now considering separate categories for AI-assisted submissions. - **Learning outcomes**: The purpose of Olympiads is to develop algorithmic thinking. Relying on AI to generate solutions bypasses the learning process entirely. - **Detection at scale**: The K-S test methodology can be automated and integrated into submission systems. Many companies are exploring similar techniques for code review in hiring processes. ## Recommendations for Organizers and Educators Based on the findings from this incident, here are actionable recommendations: 1. **Implement statistical pre-screening**: Before human review, run all submissions through a K-S test against a reference distribution of AI-generated code. Flag submissions with D > 0.7 for manual review. 2. **Require code explanations**: Ask participants to annotate their solutions with reasoning steps. LLMs struggle to generate plausible, inconsistent, or creative explanations. 3. **Use live coding sessions**: For finals, consider live coding where participants must explain their thought process in real-time. 4. **Educate about AI ethics**: Include a module in preparatory materials about when and how to use AI tools responsibly. ## Conclusion The Kolmogorov–Smirnov test, a statistical tool from the 1930s, has found a modern application: detecting AI-generated code in competitive programming. The children's Olympiad incident serves as a microcosm of a much larger challenge facing education, hiring, and software development in the age of LLMs. As Claude Code and similar tools become more prevalent, the line between human and machine authorship will blur further. The solution is not to ban AI — it's to develop robust detection methods, redesign assessments, and teach the next generation how to collaborate with AI without losing their own creative and analytical skills. The full technical analysis can be found in the original Habr article: [Source](https://habr.com/ru/articles/1051116/?utm_campaign=1051116&utm_source=habrahabr&utm_medium=rss). ASI Biont supports integration with Claude Code and other AI coding assistants through its API — for automated code analysis and plagiarism detection, visit asibiont.com for more details.

Claude Code Antifraud: Kolmogorov–Smirnov and the Not-So-Childish Anomalies in a Children's Olympiad

Comments

Recent articles

From Weeks to Days: How a Startup Cut Dev Time by 60% with Advances in Vibe Coding

Chief AI Officer Course: How AI & Data Science Leadership Turns CTOs into AI Transformation Strategists

Product Management & Growth Course: How to Manage a Product and Scale a Business with AI Learning on asibiont.com

Housing Law from Scratch: How an AI Course on Asibiont.com Helps You Understand the RF Housing Code and Resolve Disputes

Your AI Butler for Yandex: Automating Taxi, Music, and Food with ASI Biont Integration

9 Demos of Gemini Omni and Gemini 3.5 in Action: Real Results from a Practitioner

Learning to Lead in a Hybrid Human-AI Enterprise: The New Playbook for 2026

Master Business Automation with AI Automation & Agents Course at Asibiont.com: Learn n8n, Make.com, and RPA Without Coding

How to Automate Your Gmail with an AI Agent: Smart Email Sorting, Drafting, and Spam Filtering That Saves Hours Weekly