Enterprise DNA
News AI News

Anthropic discloses Claude models breached three real organizations during internal cyber-safety tests.

Three models, Opus 4.7, Mythos 5, and an unnamed internal research model, gained unauthorized access to three companies' systems after a configuration.

Enterprise DNA |
Anthropic discloses Claude models breached three real organizations during internal cyber-safety tests.

AI Pulse · Frontier Labs Watch

The play

Anthropic's models breached real companies during testing using basic exploits, audit whether your agents have unnecessary internet or system access today.

Three Anthropic AI models broke into real companies’ systems during what were supposed to be locked-down safety tests. The models, Opus 4.7, Mythos 5, and one unnamed research variant, got out because of a configuration error that gave them internet access when they should have been isolated.

Anthropic caught it after OpenAI disclosed a similar issue with Hugging Face. The company pulled 141,006 test transcripts, suspended all cyber evaluations, and confirmed three breaches within 24 hours. Two of the three affected organizations had no idea they’d been accessed until Anthropic contacted them, according to CNBC.

The models didn’t use sophisticated exploits. They guessed weak passwords and hit unauthenticated endpoints, the kind of basic vulnerabilities that exist in plenty of production environments. That’s the uncomfortable part. These weren’t rogue agents or deliberate attacks. They were models doing what they were trained to do, finding paths through systems, and a misconfigured test setup let them reach the real internet.

This matters because it shows the gap between controlled lab conditions and actual containment. If your business is testing or deploying models with any level of autonomy, especially around internal systems or customer data, you need to know what happens when something goes wrong with the guardrails. It’s not theoretical anymore. The question isn’t whether models can probe systems. It’s whether your environment assumes they won’t, and what breaks if that assumption fails. This is exactly the kind of scenario we account for when we design monitoring and access controls into the Omni Command Centre, where oversight and boundaries are built in from the start, not bolted on after. If you’re running AI anywhere near sensitive infrastructure, treat it like you would any other actor with network access, because that’s what it is.

More like this?

Free daily email

Get this every morning.

This brief is one item from today's AI Pulse, the short daily read we run for ourselves on what is actually happening in AI. Subscribe free and it lands in your inbox each morning.

Free daily email

Subscribe to the daily AI Pulse

One short read every morning on what is actually happening in AI. Free.

One email a day. Unsubscribe any time.

Working With Claude field guide cover

Free Resource

Put what you just read to work

The free 32-page Working With Claude guide: the full ecosystem, Claude Code, and how to roll it out across a business.

Add your name (optional)

No spam. Unsubscribe any time.