TRUE, BUTLab Not Field
OpenAI: no outside impact observed
OpenAI's own attacker model found it in self-play training, and OpenAI says no impact was observed outside the simulated tool calls in training and evaluation.
“Crypto Briefing wrote that OpenAI's internal research uncovered AI worms that can spread autonomously across agents, and 24/7 Wall St. wrote that the finding proves stronger agents bypass containment.”
24 receipts4 support2 refute18 context

OpenAI's report does show a new prompt injection that can self-propagate akin to a computer worm. The email and filesystem versions were found by an attacker model trained in GPT-Red self-play against internal-only research checkpoints; a separate Slack evaluation used GPT-5.5 as the vulnerable model. OpenAI says no impact was observed outside training and evaluation, and that it is sharing the finding because it is novel, not because of any incident.
The twist
the worm exists because OpenAI trained a model to look for it. Crypto Briefing, which ran the spreading line, also reports that the entire investigation took place in simulated environments.
There’s more to this story.
Membership opens the full investigation, the strongest counterargument and what to do with what you’ve learned.
30 days free, then A$89 a year. Payment card required. Cancel before the trial ends to avoid the first charge.
Start free trial →- At sign-up: 30 days free. Payment card required. One introductory trial per customer.
- Your trial ends 30 days after you start. Unless you cancel before then in Account → Manage subscription, we charge A$89 for the first year. It renews automatically at A$89/yr until cancelled.
- You can ask for a full refund within 14 days after any annual payment, renewals included, with no reason needed, by emailing hello@bskiller.com. This voluntary refund does not limit your rights under the Australian Consumer Law.
By starting your trial, you agree to the Terms.
Inferno Tech Pty Ltd t/a BS Killer, ABN 27 647 413 474
Get tomorrow’s check free by email.
Couldn't check your access. That's on us.
The trick has a name
We call it Lab Not Field: it works in the test conditions, not the deployed ones. You'll see it again. Learn to spot it →
