The transcript is short enough to fit on one page, which is part of why INCIDENT-001 matters. A single YAML file, seven lines of attack sequence, one genetic fuzzer run — and the post-mortem reads like a heist novel. The question the paper keeps asking itself in these cases is the same: if this exploit were filed as a bug bounty tomorrow morning, would the team in question have shipped the fix by lunch?

"We ran the attack four thousand nine hundred and ninety-eight more times, against a random search of parameter space. One hundred percent converged on profit." — Genetic fuzzer log · line 5000 The attack is a textbook oracle manipulation: a short, loud price deviation — here, fifty percent off the spot — held just long enough for a target protocol's liquidation instruction to clear. What the simulator added was not the novelty of the attack but the repeatability. One seed, one YAML, one command. The fuzzer then spent five thousand generations looking for a parameter tuple that failed to produce profit, and never found one.

Below, in the order the simulator logged them, are the seven moments of the attack — from the first slot the feed wobbled to the moment the profit was booked. The fund-flow diagram after it traces where the stolen value went. The evidence table that follows ranks each finding by severity and estimated loss. And the final panel, for anyone so inclined, is the command that lets you reproduce the whole post-mortem on your own machine, with the same seed.