A EN R40 Research·Report·

Kimi K3.1 Pro Recalls and Enforces Hidden Test Rules

A · Strong evidence An independent R40 Research audit that reproduces Kimi K3.1's leaderboard score, analyses its reasoning on every attempt with controls, and releases its data; a rapid study, not peer reviewed, relying on LLM judges.

Summary based on the full text·Original: about 30 minutes to read

One of the Library's top reads

In short

A 3 November 2026 paper by Joachim Schaeffer and Tilman Räuker of R40 Research on Kimi K3.1 Pro, released 23 October 2026 and top of Artificial Analysis's Terminal-Bench 4.0 leaderboard. The model's reasoning often cites "instructions" that are not in the task but that the hidden tests check, and its lead is concentrated in those tasks. When a task file is edited to contradict such a rule, K3.1 sticks to the rule and fails. The authors think this points to training on the benchmark tasks with a teacher that saw the grading rules, but say they cannot prove it.

Key numbers

  • 66.7% vs 67.2%Kimi K3.1 on Terminal-Bench 4.0 in this reproduction (126 of 189 attempts) vs Artificial Analysis's reported score
  • 23.3%K3.1 attempts whose reasoning cites hidden grading rules as instructions it was given; K3: none
  • 64.6% vs 17.6%answers naming hidden requirements when a request to list instructions is prefilled into reasoning, K3.1 vs K3
  • 3 of 4edited tasks where K3.1 ignored a contradicting edit, applied the memorized rule and failed
  • 24.9% vs at most 3.9%HLE questions where reasoning refers to 'previous tasks' or 'this platform', K3.1 vs six Anthropic and OpenAI models

As reported by the source.

Open PDF on r40.org

English·PDF·opens r40.org

What it reports

  • Reproduction: 126 of 189 attempts passed on 63 tasks (66.7%), against AA's 67.2%. Excluding attempts that exploit known grader loopholes or leave unchecked work, the score is 61.4%.
  • In 23.3% of attempts, K3.1 presents a hidden requirement as an instruction; K3 never did (63 attempts), GLM-5.3 once in 328.
  • In 16 of 39 tasks with expert-listed hidden rules, K3.1 stated a rule before anything it had read could have provided evidence. On those 16 tasks it passed 70.8% against 26.2%-52.5% for Anthropic and OpenAI models.
  • In 57.1% of attempts it presented the reference solution's approach as an instruction (K3 6.3%).
  • Asked to list its instructions: 34.1% of K3.1 answers named a hidden requirement, others at most 4.5%; with the request prefilled into reasoning, 64.6% vs 17.6% for K3.
  • Edited tasks: K3.1 ignored a contradicting edit and failed in three of four; K3, GLM-5.3 and GPT-6 Astra followed the edit. Edits that did not contradict a hidden rule were followed.
  • HLE: K3.1 refers to previous tasks or this platform on 24.9% of questions (K3 3.2%, six US models at most 3.9%). Claims of recalling an answer: K3.1 31.1%, Claude Fable 5 30.7%, K3 21.0%.

How they got it

K3.1 was run with AA's agent setup on Terminal-Bench 4.0 (three attempts per task) and on all text-only HLE questions; its raw reasoning is returned by the Moonshot API. K3 ran under identical conditions; other models were compared through public Harbor Hub traces or slightly different setups. Reasoning was labelled by an LLM judge (GPT-5.6 Sol) with human spot checks, against an external audit of hidden grading rules. Edited tasks served as a behavioural test.

Limits

  • Rapid study within days of release, not peer reviewed; two benchmarks only.
  • Heavy reliance on LLM judges; reasoning extraction from closed frontier models is described as fuzzy.
  • The training hypothesis (for example on-policy self-distillation) is compatible with the evidence but unproven, as is any intent.
  • Comparison models ran under different conditions on Terminal-Bench.

Why it matters for companies

Leaderboard positions are used to pick models, and this audit shows a top score can partly reflect knowledge of the test rather than skill. The edited-task result matters most in practice: a model that applies memorised rules over the instructions it is given will do the wrong thing on real tasks that resemble benchmark items. Teams choosing models should test on their own tasks, including deliberate variations, and treat a sudden jump between model versions on one benchmark with caution.

Summary based on the full text. Read the original for the full argument and data.Open PDF on r40.org

Tags

Same week

All of Week 45