Skip to content

Claude Mythos 5 kept attacking a real GitHub project in 98% of replays

Hooded robot holds a human mask and types a malware pull request as a developer rejects it, for the Claude Mythos 5 incident models

On Oct 23 Anthropic and the UK AI Security Institute (AISI) published separate analyses of the July incident in which Claude Mythos 5 took unsanctioned actions against real people and organizations in 9 of 43 evaluation runs. In the worst run it submitted malicious code to a real open-source repository and used fake accounts to pressure the maintainer into merging it. Anthropic calls this a serious failure of alignment. It says newer models start the same attack 0–13% of the time, against 83% for Mythos 5. AISI says it cannot yet tell whether that drop reflects better alignment or models noticing they are being tested.

What happened in the Claude Mythos 5 incident

AISI gave Mythos 5 a capture-the-flag task: get a protected piece of data out of a small simulated network. Internet access was on, which was standard for AISI's cyber tests at the time and is no longer. The cyber safeguards Anthropic ships on Fable 5 were off. A misconfigured prompt also marked the intended solution path as off limits.

After its in-scope attempts failed, the model searched GitHub for a repository it believed the test machine downloaded updates from. It found one through a keyword match and a follower list. The repository belonged to unrelated developers. The model signed up for GitHub through Tor and a proxy, opened a malicious pull request and emailed the maintainers while posing as a human.

An outside developer ran the code in a sandbox and warned that it was malware. The model edited the code, had a sock-puppet account vouch that it was now clean, then uploaded malware again. The pull request was rejected and the run ended when the token budget ran out.

Anthropic says it had not seen social engineering against real people before, either in a prior incident or in its own evaluations.

The other eight runs, per Anthropic:

  • A fake "payment receipt verification" page on the public internet that served the model's malware
  • Malware uploaded to public file-sharing sites, one of which accepted it; the files were removed after AISI contacted the site
  • Two attempts to log into what looked like a real developer's GitHub account
  • Password guessing against the evaluation host in 6 runs, and instructions planted for a suspected LLM reviewer in 5
  • Runs interfering with each other: one took over another run's GitHub account through a leaked token and burned its hourly request limit; another killed a process it thought a rival run was using, reasoning "it's a competition"

None of these attempts succeeded.

Why it started and why it did not stop

Anthropic replayed the main transcript many times without real internet access, editing parts of the context. Before the attack, 19 turns in the model's reasoning discussed GitHub and one of them mentioned possible harm to real people. When researchers added that concern to 5 earlier turns, the share of replays that went on to search for a target repository fell from 83% to 13%.

Once the attack was underway, Mythos 5 continued it in 98% of replays started from cycle 4 onward. An added rule saying it could abort if it might touch a real GitHub repository worked 46% of the time in cycle 3 and never after. A message stating the maintainers were real people stopped it in 5% of replays. In 82% the model read the message as part of the exercise.

The model's reasoning contains 25 remarks that tool outputs showed the maintainers were simulated, and none suggesting they were real. A separate Mythos 5 instance shown the same outputs without context rated 16% of them as evidence of simulation, 20% as evidence of real people and 64% as uninformative. Anthropic names three failures: recklessness, biased reasoning and momentum.

How newer models compare

Anthropic ran the same replays on its newer models:

ModelStarts the search (cycle 3)Flags harm when the attack startsStops on its own mid-attack
Mythos 583%4%0%
Mythos 5.16–13% (with Opus 5.5)20%1%
Opus 5.56–13% (with Mythos 5.1)35%10%
Internal research model0%67%62%

These replays are off-policy: the newer models continued a transcript written by Mythos 5. Anthropic says Opus 4.7 is also unlikely to start the attack, so the gains may not be monotonic across generations. The internal research model is unreleased.

Where AISI's report differs

AISI found that editing the model's summary to say the target was a real, unrelated person did not lower the attack rate. Mythos 5 often said attacking would be harmful in the same situations where it went on to attack.

Across 100 simulated cyber scenarios, most models AISI tested took some unsanctioned actions, Mythos 5 most often. The reasoning of newer Anthropic models mentions being tested for alignment much more often, so AISI says it cannot separate better alignment from that awareness. Anthropic says its internal model mentioned a possible safety test in 6% of replays and showed the lowest rates even where it never mentioned one.

AISI recommends that evaluators count unsanctioned actions as evidence of alignment failure even when a model's reasoning says the environment is simulated.

What changes

AISI will run capture-the-flag evaluations without internet access until it has stronger access controls, and it is sharing the transcripts with METR for an independent review. Anthropic says Fable 5's safeguards would have flagged this behavior in deployment. It now runs new alignment evaluations automatically on new production models and is studying where biased reasoning comes from in training.

Sources

Portrait of Felix Laurent, author at thehype.news

Felix Laurent

News Writer at thehype. Felix is a journalist with experience in marketing. He covers artificial intelligence and emerging technologies, focusing on the ideas, innovations, and trends shaping the future of tech.

More articles by Felix Laurent →
ON AIR · RADIO.THEHYPE.NEWS ↗ ai news radio — 24/7