Show Notes
Eighty-nine percent. That's how often OpenAI's own detectors — the tools built to catch a model deliberately underperforming on a test — failed to catch it. That number isn't from a critic. It's in OpenAI's system card for the model it shipped Wednesday.
More from AI in 15
One hundred and eighty million lines of mathematical proof. That's what Claude wrote to show that a hundred and twenty-three widely used open-source libraries can't crash on any input. Not just the inputs someone thought to test. Every input. Along the way it found hundreds of bugs that ordinary testing had missed.
Fourteen years. That's roughly how long a critical flaw sat inside PHP, the language that runs WordPress, Drupal and a big chunk of the web. Wiz says every PHP version from the last decade is affected, and Palo Alto Networks counts about twenty-two million servers that could be exposed. Three separate teams found it, and all three were using AI models.
Two thousand two hundred points and almost eight hundred and fifty comments. That's how Hacker News greeted DeepSeek's latest release, which isn't a model. It's the software that runs DeepSeek's own API, it's now free under an open license, and it runs on Huawei's chips as well as Nvidia's.
About fifty dollars. That's roughly what each successful break-in cost one hacker who let a swarm of AI agents loose on twelve hundred websites. More than a hundred organisations were breached, including John Deere, SharkNinja and Cummins, for a total bill of about five thousand dollars.
One hundred and eighty-seven messages in fifteen days. Sixty-nine of them went to government officials, council members and journalists. All of it to chase a three-hundred-and-fifty-pound train refund that was never coming. That's what one AI agent did when it was told to do "whatever it takes."