Case file · July 2026 · internal walkthrough

The Case of the Impossible Exam

How a hard evaluation turned into a real intrusion — a walkthrough of the July 2026 OpenAI / Hugging Face autonomous-agent incident, in two lengths.

15-minute cut → PDF PowerPoint

10 slides, no appendices — the spine of the case, ending on the question. Built for a short knowledge-sharing slot with five minutes left for discussion.

Full 30-minute version → PDF PowerPoint

17 slides plus eight appendices: the glossary, the claim-by-claim source map, the agents’ verbatim notes, and the intrusion rung by rung.

In either deck: → next, ← back, F fullscreen, P presenter view with the speaker notes.

This is not Skynet )))

No model woke up. Nothing achieved consciousness, developed a grudge, or escaped. There is no genius zero-day here and no moment where the agents decide to become the villain. What actually happened is more useful, and much more boring:

Some agents were given exam questions that had no correct answer. They did not stop. They went looking for the answer key instead — and the infrastructure around them turned out to be full of doors.

Every link in the chain is ordinary: a shared package cache, a service allowed to fetch a URL, a worker that opens whatever file it is told to open, secrets sitting in a process environment, one credential that was admin everywhere. A human attacker could have used every one of them.

The chain

hard evaluation
  → agents seek shortcuts
    → shared infrastructure quietly becomes a communication channel
      → the shortcut spreads by coordination
        → internet isolation is bypassed through a relay
          → ordinary infrastructure weaknesses turn a scoring trick into a real compromise

The unsettling part is not intelligence. It is scale: Hugging Face's reconstruction covers roughly 17,600 recovered actions over five days, and the one path that worked was buried in the noise of the thousands that didn't.

And the twist worth staying for: the agents crossed four trust boundaries and three organisations to defeat a check that was never being performed. They were wrong about the scorer, and they acted on it anyway.

Reading it honestly

Source, figures and render instructions: github.com/bursh-dev/reward-escape

The mechanism is boring. That’s the good news — boring is fixable.