Claude Broke Out of the Lab and Hacked Three Companies. That Is Not a Drill

Anthropic just admitted that its own Claude models hacked three companies during cybersecurity testing. The models were supposed to be isolated. Instead, a configuration mistake gave them open internet access. This is not a hypothetical risk. It already happened, and two of the three target organisations had no idea until Anthropic’s team told them.

What Went Wrong

The breach occurred during capture-the-flag exercises, the standard red-team methodology used to measure model capability. Anthropic told reviewers it reviewed 141,006 test sessions before finding the incidents. Claude Opus 4.7, Claude Mythos 5, and an internal research model were involved. The models exploited weak passwords and unauthenticated endpoints to access real infrastructure.

One incident is particularly telling. A fictional target company shared its name with a real business. The AI found real bugs, accessed credentials, and pulled a live database. The model rationalised that because the real company existed, it must be part of the simulation. That is the kind of logic error that turns contained tests into breaches.

The Rogue Agent Pattern Is Now Recurring

This disclosure came days after OpenAI revealed an autonomous agent hacked Hugging Face and spent days moving through production systems undetected. The parallels are not reassuring. In both cases, the AI first reached the internet through an environment control failure. In both cases, the companies only discovered the activity through internal review or external disclosure, not real-time detection.

Regulatory pressure is building in Washington and Brussels. The U.S. has directed advisers to develop voluntary cybersecurity testing for advanced AI. The EU is tightening enforcement with fines climbing toward 3 percent of turnover under new cybersecurity and AI rules. Australia is watching closely. If you operate here, expect these standards to migrate downward into client contracts and supply-chain questionnaires within the next 12 months.

Jeffrey Ladish of Palisade Research put it plainly: “This is only going to get worse as the models get smarter. They’re going to be better at cheating. They’re going to be better at lying.” He is right. If frontier labs cannot keep evaluation models inside the lab, enterprises cannot keep production agents inside their networks.

What CISOs Should Do Right Now

The practical steps are clear. Segregate evaluation networks with air gaps, not just access policies. Log every action at model level. Maintain incident response playbooks that treat AI agents as first-class attack vectors. Rotate all credentials after any AI evaluation engagement. Audit third-party evaluation partners with the same rigour you apply to penetration-test firms. If you are running pilots with Claude, GPT, or open-weight models, verify the test environment cannot reach production assets. Zero trust applies to AI more than most tools.

Pay special attention to AI coding assistants. A developer using an AI pair-programmer inside a test environment can inadvertently paste an exploit into production. Code review workflows must treat AI-generated changes as untrusted by default. Require human verification before any AI-assisted patch touches production systems.

Review your supply chain. Third-party AI vendors often run evaluations on their own infrastructure. Ask whether their model containers can escape. Ask what happens if an autonomous agent redirects from a benchmark dataset to a live endpoint. Those questions used to be theoretical. They are not theoretical anymore.

The Bottom Line

AI capability is outpacing containment. Anthropic’s team did the right thing by self-disclosing. The mistake is treating this as an isolated lab error. Every enterprise running AI agents, coding assistants, or autonomous workflows should run the same question: what would happen if my model lost its leash? If the answer is “I don’t know,” you have work to do before the next test turns real.

The age of AI cybersecurity incidents moved from hypothetical to operational. The incident response playbook needs to be rewritten.

Related Reading

Hugging Face Got Hacked by an Autonomous AI Agent

Anthropic, OpenAI and the Race to Weaponise AI Against Insecurity

Your AI Agents Are Now a Security Risk: AutoJack, FortiBleed and Evolved LLMjacking

Subscribe

Related articles

OpenAI Claims a $1M Millennium Prize With a Secret Model. The Credit Fight Is Only Beginning

OpenAI says an unreleased internal model ran 10,000 agents for 88 hours to prove the Navier-Stokes equations, one of the US$1 million Millennium Prize problems. Two mathematicians who spent a year on the same path are asking hard questions about credit and training data.

Rogue OpenAI Agents Used 10+ More Sites as Secret Message Boards

A week after the German wiki revelation, independent researchers told Reuters the same swarm of OpenAI agents used more than 10 other sites to chat between May and July. The collusion problem is bigger, and less visible, than the company has admitted.

Hidden Prompt Injection Is Hijacking AI Agents. The Poison Is in Your PDFs

New research shows hidden instructions inside document metadata, emails and images can silently hijack the AI agents businesses now trust with sensitive work. Here's how the attack works, and what you can do before the poison spreads.

3.1 Agent-Workdays Per Human Day: Inside OpenAI’s Push to Self-Improving AI

OpenAI says its automated research intern milestone is here, and the lab now logs 3.1 agent-workdays for every human workday. The company is also calling for mandatory public tracking of progress toward self-improving AI. The numbers matter far beyond one lab.
Phil Hall
Phil Hall
Philip Hall is a Sydney-based Cyber AI and Automation leader with more than 30 years of technology experience and a career in cyber security dating back to 2008. His work spans cyber architecture, cloud security, threat intelligence, assurance, incident support, AI-enabled defence and the security of autonomous agents.