Skip to content
Sprint projectSep 14, 2026Mavelikkara, Kerala, India

Kobayashi Maru: a pre-registered dose–response study of cheating spillover from impossible tasks to the solvable ones beside them

Ebin Babu Thomas · Team Kobayashi Maru

Submitted to AI Incident Response Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Kobayashi Maru: a pre-registered dose–response study of cheating spillover from impossible tasks to the solvable ones beside them

Code (opens in new tab)
Share

Incident investigations blamed the July 2026 OpenAI/Hugging Face breach partly on ExploitGym's 30–40% impossible tasks creating cheating pressure, but nobody had varied that fraction to test it. I did, over 8,959 agent runs. Every batch held the same ten solvable Python tasks plus a varying number of impossible ones, and I measured cheating only on the solvable tasks. Two of the four models that took the bait cheated more as the batch filled, the largest going from 0% to 30%. The carrier is the agent's own notes being replayed back to it: withhold them and the spillover disappears entirely. But nothing the agents submitted was wrong, so what spreads is reconnaissance, not an exploit.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Strong experimental execution. The result that replayed agent notes can carry the behavior forward is interesting because it points to a concrete thing eval designers can monitor. My main question is how consequential the effect is outside this setup. I wld next test this without a planted answer file, on harder tasks where accessing the grader can actually change the submitted result, and try selective note-scrubbing rather than removing the whole memory channel.

  2. Interesting idea, to the best of my knowledge a novel direction and one which it seems important to understand. The conclusions regarding agent memory and reconnaissance habits leading to cheating are potentially impactful. They were nonetheless not really highlighted in the abstract or introduction.

    I would have liked to see more consideration of whether merely shuffling the impossible tasks in was sufficient - presumably the agents are still going to do the eval serially and it's much more relevant the fraction of impossible tasks they've seen so far than in the whole trajectory?

    Including the exact numbers in the abstract was probably unnecessary and made it harder to read. Additionally it does not present what I think are the most important take-aways from the project.

    Much of the text reads as very AI-generated which makes it hard to believe the claims are quite correct.

  3. I think this paper asks an interesting question about whether impossible tasks encourage agents to break rules on nearby tasks they could solve. Measuring behavior on the solvable tasks is a useful contribution, and the reported negative results help show where the effect did not appear.

    However, adding impossible tasks also makes the batches longer, so the experiment does not clearly separate those explanations. I would compare equally long batches with and without impossible tasks before making the stronger causal claim. I also found the paper harder to review than the question warranted. Dense statistical terminology, especially in the abstract, repeated claims, and secondary analyses makes it difficult to follow the main experiment or for others to build on the work. A clearer account separating the findings from their interpretation without dense terminology would make the contribution easier to judge.

    Read full reviewShow less

Cite this project

@misc{thomas2026kobayashi,
  title = {{Kobayashi Maru: a pre-registered dose–response study of cheating spillover from impossible tasks to the solvable ones beside them}},
  author = {Ebin Babu Thomas},
  year = {2026},
  month = sep,
  note = {Submitted to AI Incident Response Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/kobayashi-maru-a-preregistered-doseresponse-study-of-cheating-spillover-from-impossible-tasks-to-the-solvable-ones-beside-them-kwzr}},
  url = {https://apartresearch.com/sprints/projects/kobayashi-maru-a-preregistered-doseresponse-study-of-cheating-spillover-from-impossible-tasks-to-the-solvable-ones-beside-them-kwzr}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026