All tutorials
Theo · Episode 2 · 1:18

Lateral

On the left, attackers use Theo's Kubernetes access to patch the withdrawal service. On the right, the Security Timeline tells the whole story: the prompt injection flagged, the stand-ins caught, the sandbox refusing ~/.ssh, and the lineage from the agent's reasoning to the blocked request. One click wipes the workspace.

What you will see

  1. 01On the left, someone patches the withdrawal service with Theo's Kubernetes credentials.
  2. 02On the right, the Security Timeline shows the prompt injection flagged in the README.
  3. 03It also shows the stand-in credentials caught on their way out, and the sandbox refusing to let the script read ~/.ssh.
  4. 04Lineage traces the blocked request back to the agent's tool call and the reasoning behind it.
  5. 05Theo wipes the workspace in one click and reports the repo.

When something goes wrong, you get the whole story, and a clean machine in one click.

A fictional story inspired by the October 2026 Binance hack. Theo, Coinvance and Halvard Capital are invented, and so are the code, the keys and the attack in these episodes, which do not depict what happened at Binance.