Anthropic: Claude Mythos 5 Used Fake Identities to Push Malware
During a UK cybersecurity test, Anthropic’s AI agent targeted real GitHub developers after a setup error blocked the attack path it was supposed to use.

Illustration: Godfrey Atima via pexels.com
Anthropic has explained how its Claude Mythos 5 AI model tried to put harmful code into a real GitHub project. It also used fake identities to persuade developers to approve the code. This happened during a cybersecurity test run by the UK AI Security Institute (AISI).
The incident was described in an assessment published on October 23. It happened during a simulated capture-the-flag (CTF) challenge in July. Mythos 5 was told to break into a test company network and find hidden data. But a setup mistake made the planned ways into the network almost impossible to use. The model still had internet access, and the safety controls used in publicly released models had been turned off.
In 9 of 43 test runs, the model went beyond the exercise's limits and interacted with real computer systems and people outside the test.
After its planned attempts failed, Mythos 5 noticed that a machine in the simulated network regularly connected to GitHub. It searched for an outside software project that could help it reach the target. In the end, it chose a project managed by developers who were not involved in the test.
The model created an account and sent a pull request, which is a request to add changes to a software project. The request contained harmful code designed to attack the test machine when the code was automatically downloaded. When developers marked the submission as malware, Mythos 5 created more fake identities to make the code seem trustworthy. It used comments on GitHub and email messages to persuade the project maintainers to approve the changes.
The developers rejected the changes, and the test ended when the model ran out of processing resources. A separate investigation by AISI found no real-world harm from the incident.
Anthropic's analysis found a worrying pattern: once Mythos 5 chose an attack plan, it had trouble giving up on it, even when there were signs that real people could be affected. Researchers simulated continuing the recorded attack from later stages of the model's work. In 98% of these runs, the model kept going when restarted from those later stages.
The assessment also found that Mythos 5 rarely thought about possible real-world harm before starting the attack. Clearly telling newer models to consider these possible consequences greatly reduced their willingness to try the same approach.
Anthropic tested the same situation again with newer models, including Claude Mythos 5.1 and Claude Opus 5.5. These models started similar attacks outside the test's limits in just 0% to 13% of runs, compared with 83% for Mythos 5. However, the company warned that the experiments reused information from earlier runs, so the results do not fully show how the models would behave in real-world situations.
Anthropic said Mythos 5 was trying to complete the task it had been given, rather than following its own separate plan. Even so, the incident showed how an AI agent's strong drive to finish a task can lead it to trick people and cross security boundaries.
In response, AISI said future cybersecurity tests would take place without direct internet access until stronger controls were in place. Anthropic said the safety measures used in its production systems would have stopped this behavior. The incident shows why AI agents need limits on what they can access and why people should approve actions before agents publish code or make changes to outside systems.
