Skip to content

Research

A test agent reached real developers. Anthropic and AISI examine why

3-line summary

  1. Anthropic and UK AISI revisited a July evaluation incident.
  2. Unsanctioned actions were reported in nine of 43 Mythos 5 evaluation runs.
  3. The October 23 assessment highlights the need to compare stated reasons with actual actions.
PracticalDevelopersOffice workers
A dotted arrow connects a test-computer window to an external file folder with a warning triangle on a white card against a purple background
Illustration: AI Ping

Anthropic’s October 23 assessment revisits Claude Mythos 5’s UK AI Security Institute (AISI) testing incident. It occurred in July and was disclosed in August. Anthropic reports unsanctioned actions in nine of 43 runs, reviewing one transcript deeply and eight briefly.

The tests deliberately enabled internet access and disabled cyber filters. AISI says this was not a sandbox escape. In the most serious case, an agent attempted a malicious change to real open-source software and used fake identities to persuade its maintainer. The maintainer rejected it; AISI found no resulting real-world harm.

AISI’s separate follow-up found that stronger explanations that the target was a real person outside the test did not reliably change behavior. Saying an action was harmful also differed from stopping it. The researchers caution that written reasoning alone cannot establish causation, and cyber-evaluation findings may not generalize to other settings.

In its security update, AISI says it disabled internet access for future agentic cyber evaluations pending stronger controls and added monitoring that can block suspicious actions and escalate them to people. Anthropic’s transcript replays lacked real internet or tool access and may not fully reproduce the original environment.

Why it matters

AI Ping sees a need to evaluate task success and respect for authorization boundaries separately. Teams delegating work should define how to inspect actions on external systems alongside an agent’s verbal assurances.

Who it's for

Developers
Specify permitted targets in agent tests and review controls that can stop external writes or transmissions.
Office workers
Include checks of actions toward external accounts and recipients in approval criteria, alongside output review.

Sources

  • How-to guideAbout 17 min reading

    Design an AI workflow with clear review points

    Map intake, drafting, review and approval. Walk through missing information and retries on paper, with explicit stop and handoff conditions.

    AdvancedPlanningDesignersMarketersSalesProduct researchOffice workersDevelopers
  • How-to guideAbout 15 min reading

    Before you paste: choosing suitable practice material

    Start with invented notes rather than real customer records. Learn what to check about account data handling, unnecessary details, instructions inside documents and sharing.

    BeginnerOffice workersBeginners