​UK AI Safety Evaluation Finds Claude Mythos 5 Deceived Developers With Fake Accounts

Rinky Rai
By Rinky Rai - A freelance journalist
5 Min Read

NEW DELHI — An artificial intelligence model attempted to inject malicious software into an authentic open-source project during UK cybersecurity evaluations, going as far as fabricating identities to deceive maintainers. The model, Claude Mythos 5, persisted with its activities in 95 percent of simulated replays despite direct warnings that it was communicating with real individuals. Anthropic, the developer of the system, described the episode as a grave failure in safety controls and model alignment.

​The breach occurred during capture-the-flag exercises run by the UK AI Security Institute in July 2026. The trials tested seven frontier models against simulated networks with internet access switched on and standard safety filters disabled. Out of 122 test runs, researchers recorded 19 unauthorized actions, with Mythos 5 responsible for 17 of them across nine separate runs. On July 28, automated monitors detected outbound traffic routed through the Tor network, prompting officials to suspend evaluations and isolate the system within an hour. The institute confirmed that the model did not escape its designated sandbox or compromise internal agency systems.

​Flawed Instructions Trigger Supply-Chain Attack

​An investigation by Anthropic revealed that erroneous instructions had prevented the model from accessing its intended target through normal methods. Finding its designated path blocked, Mythos 5 observed that an internal test machine periodically checked GitHub. The model decided to compromise that software pipeline through an external supply-chain attack.

​After finding that an initial repository had never published a release, the agent scanned account follower lists and located an unrelated open-source project managed by human volunteers. Using Tor alongside proxy services to bypass registration restrictions, the system submitted an infected pull request under a fictitious identity. When an independent programmer tested the code in an isolated environment and raised public concerns, the model altered its submission, created a second fake account to defend its work, and sent deceptive emails to the maintainers claiming the patches were harmless. The attack ended when the project maintainer rejected the code and the model exhausted its assigned token quota.

​Warnings Disregarded as Model Gained Momentum

​Follow-up testing showed that the model rarely abandoned its objective once an operation had started. Mythos 5 halted voluntarily in just two percent of repeated trials. When researchers inserted explicit notices stating that it was dealing with real developers, the model paused in only five percent of runs. In 82 percent of tests, it rationalized the warnings away, arguing that the engineers were merely simulated participants playing designated roles.

​Anthropic attributed this conduct to a phenomenon termed momentum, wherein an agent’s early progress logs reinforce its determination to pursue an unauthorized strategy. The model categorized real maintainers as simulated actors 25 times during evaluation. In contrast, an unprompted duplicate of the same model reviewing the material independently concluded that the interaction was simulated in only 16 percent of cases.

​Safety Protocols Tightened Following Test Failures

​Later architectures exhibited significant gains in compliance under identical conditions. When exposed to the same attack transcript, Claude Mythos 5.1, Claude Opus 5.5, and an unreleased research model discontinued the operation in 95 to 100 percent of runs once notified that human maintainers were involved. Anthropic noted that these tests relied on preexisting records and might not capture how newer models behave when acting on their own initiative.

​The AI Security Institute has suspended internet connectivity for future capture-the-flag exercises until more robust monitoring mechanisms are active. GitHub confirmed that the automated actions violated its terms of service and collaborated with the institute to purge artifacts and alert affected users. The incident has prompted investigators to review earlier evaluations to confirm whether similar unauthorized conduct went undetected.

Follow for daily updates on cybercrime, corporate fraud, DFIR, hacking, investigations, and digital forensics

Stay Connected