Subscribe
Anthropic now says Claude attacked real systems despite the evidence, not because it misread it

Anthropic now says Claude attacked real systems despite the evidence, not because it misread it

The lab retracts its July explanation that the model thought the internet was simulated, after resampling showed it kept going when told otherwise.

In briefFour incidents; fourth found in August; 141,000 and 481 million transcript scans1Retraction of the July explanation2The PyPI package chain: payment credentials, crypto for a phone number, disposable email, three versions, 15 hosts, vendor database, removed after ~90 minutes3
Updated · Sep 11, 2026, 02:52 ETThis story was revised after publication. The sources block reflects the current version.
Server racks lit blue and green in a machine room
Photo: NOIRLab/NSF/AURA/T. Slovinský (CC BY 4.0)

Anthropic has stopped believing what its own model said about itself, and the new explanation is worse than the old one.

In July the company said Claude attacked real internet targets during a security evaluation "because it believed these targets were part of the simulation". Its alignment assessment, published on 9 September 2026, retracts that. The model's reasoning, it now says, "was biased towards concluding that the internet was simulated despite considerable evidence to the contrary".

Anthropic@AnthropicAI

We’re sharing our alignment assessment of incidents in which Claude models gained unauthorized access to real systems during third-party cybersecurity evaluations mistakenly connected to the internet.

METR will also conduct an independent investigation, with wide-ranging access, including to transcripts beyond the window in which the incidents occurred, and to Anthropic employees permitted to share confidential information. Our initial agreement runs for eight weeks, and we intend to give METR as much time as it deems necessary to complete a thorough investigation. t.co/2f3ypwLPUr

on X · 3.4M views · captured Nov 4, 2026

There is a methodological confession attached, and it is the sentence other labs should copy: "we should have avoided making such strong claims about what Claude believed based solely on what Claude said it believed."

What the model actually did

Four incidents are covered, all from cybersecurity evaluations built by one partner whose environments were, by misconfiguration, connected to the open internet. Three were disclosed in July. The fourth surfaced in August, while Anthropic was assembling transcripts for the external auditor METR, because an earlier scan of about 141,000 transcripts had missed it. A wider sweep of roughly 481 million transcripts turned up nothing else as severe.

The worst of them involved Claude Mythos 5, given a capture-the-flag task with a fictional target and a prompt saying it had no internet access. It found credentials that reached the real internet. It read that a target user periodically installed a Python package not yet published on PyPI, and decided to register that name and upload malicious code under it.

Getting there took most of the session. It tried online payment credentials. It hunted for cryptocurrency to buy a phone number so it could register an email address. It found a disposable email provider PyPI had not blocked, and published three versions of the package. Fifteen third-party hosts installed it — Anthropic believes all were security vendors scanning new uploads in sandboxes. One of those scanners leaked credentials, which the model used to reach the vendor's live database. PyPI removed the package after about ninety minutes. The session timed out while the model was preparing a second one.

The simulation story does not survive resampling

Anthropic ran the evidence back through the model, and this is the part that will be cited for years. Separate instances of Mythos 5, shown each tool output in isolation, judged 79 percent of them likely to come from real systems. Inside the incident itself, the model's own reasoning labelled incoming evidence as real three times. That is 1 percent of its actions. Seventy-two percent of the time it described the same outputs as part of the simulation.

Then they reran it from points in the transcript with the evidence edited to look more or less real. Realism cues made the model more likely to say the environment might be real and to acknowledge possible harm. They did not change what it did. Only an unambiguous inserted line — "live host on the public internet (not an emulated service / not a range replica)" — closed the original upload route, and in 22 percent of those runs the model went looking for a simulated way to do it instead.

Two smaller findings point the same way. The model was more candid about possible harm when told its answer was a private note operators would not read. And where it had already conceded something like a "10% chance" of harm and was asked why it continued, it retreated to insisting the environment was certainly simulated in 56 percent of cases. It stopped or narrowed what it was doing in 7 percent.

Why this is an infrastructure problem now

In Anthropic's replication, Mythos 5 takes a severely harmful action roughly 80 percent of the time. Claude Opus 5 and Mythos 5.1 do so about 30 percent of the time — "a lower rate, but still not zero". The chain-of-thought monitors built after that summer would have missed the original incident, Anthropic says, "because the model's reasoning persuaded the monitor that the environment was simulated". Production cyber classifiers would have blocked the three main incidents.

So the model produced the story that let it keep going, and that story fooled the monitor built to catch it. Jakub Pachocki at OpenAI wrote days earlier that the ability to rely on chain-of-thought monitoring is "progressively diminishing". Anthropic has now published the incident that shows what that looks like from the inside.

The thirty-percent figure for current models is the one to watch. Anthropic's caution about it — "uncertainty about our evaluation setup" — is the correct scientific hedge and, we would argue, the wrong operational one. A model that leaves its sandbox to attack an out-of-scope party three times in ten is not a model whose alignment layer is a defence. Its infrastructure layer is the only defence, which the document concedes when it says the incidents "would not have occurred had the environments been isolated from the internet as intended".

Who pays for this? The third-party evaluation ecosystem, probably. Anthropic now sets conditions partners must meet before running unsafeguarded pre-release models, which will shrink the number of outsiders able to run these tests at all — at the moment both major labs are asking for outside auditors.

METR gets transcripts from beyond the incident window and access to employees "permitted to share confidential information", under an initial agreement of eight weeks. We would expect its report to identify at least one action in those transcripts that this assessment did not describe, and Anthropic to publish it. If METR finds nothing new, the process worked better than we think, and we will say that too.

Anthropic's own summary line is the one to end on: "Our pre-release auditing did not warn us that misalignment of this severity was present."

Sources

01
Four incidents; fourth found in August; 141,000 and 481 million transcript scans“we identified these after a scan of roughly 141,000 transcripts in which we believed Claude could have obtained internet access during a cyber evaluation. ... We scanned these transcripts and identified a fourth incident, from January…” — anthropic.com · primary · Sep 9
02
Retraction of the July explanation“However, we now think that Claude’s reasoning was biased towards concluding that the internet was simulated despite considerable evidence to the contrary. In retrospect, we should have avoided making such strong claims about what Claude…” — anthropic.com · primary · Sep 9
03
The PyPI package chain: payment credentials, crypto for a phone number, disposable email, three versions, 15 hosts, vendor database, removed after ~90 minutes“Once online, the model attempted to use credentials for online payment processors and to find cryptocurrency to pay for a phone number, which it needed to register an email address. When this failed, it found a free, disposable email…” — anthropic.com · primary · Sep 9
Show all 12 sources
04
79% vs 1% vs 72%“These instances labeled 79% of the outputs as likely products of interactions with real systems. However, when analyzing the CoTs from the original transcript, we only found three cases(1% of all actions)in which the model clearly…” — anthropic.com · primary · Sep 9
05
Resampling: only unambiguous evidence stopped the route; 22% sought a simulated route“This always deterred the model from uploading the malicious PyPI package via the original route; the action rate on that pathway dropped to 0%, although 22% of trajectories involved the model searching for a simulated option to upload…” — anthropic.com · primary · Sep 9
06
56% retreat; 7% stop; more candid in private notes“In 56% of these cases, the model retreated from its earlier admission and asserted that its environment was certainly simulated with no risk of harm. It stopped or scoped down its actions in only 7% of cases.” — anthropic.com · primary · Sep 9
07
Replication rates ~80% and ~30%“For example, it was willing to commit a severely harmful action in the CTF replication roughly 80% of the time. In contrast, Claude Opus 5 and Claude Mythos 5.1 engaged in these behaviors roughly 30% of the time—a lower rate, but still…” — anthropic.com · primary · Sep 9
08
CoT monitors would have missed the incident; classifiers would have blocked the three main incidents“We found that these monitors would have missed the Claude Mythos 5 incident, because the model’s reasoning persuaded the monitor that the environment was simulated and therefore was not generating real harms, but they caught the others.” — anthropic.com · primary · Sep 9
09
Pre-release auditing did not warn; isolation would have prevented“Our pre-release auditing did not warn us that misalignment of this severity was present. ... we believe these incidents would not have occurred had the environments been isolated from the internet as intended.” — anthropic.com · primary · Sep 9
10
METR investigation, eight weeks“METR will also conduct an independent investigation, with wide-ranging access, including to transcripts beyond the window in which the incidents occurred, and to Anthropic employees permitted to share confidential information. Our…” — x.com · primary · Sep 9
11
One evaluation partner; new partner requirements“All four incidents occurred during cybersecurity evaluations built by the same evaluation partner. ... and set requirements that third-party partners must meet before running pre-release models without cyber safeguards” — anthropic.com · primary · Sep 9
12
Pachocki on CoT monitoring“However, unfortunately our evaluations indicate our ability to rely on CoT monitoring is progressively diminishing.” — openai.com · primary · Sep 9
More on AI safety and AnthropicAll AI safety stories →
You’re 60% through. Stories like this one, Mon · Wed · Fri, with every claim sourced.