Humanity & AI Safety Accord
Menu

Incidents

Level 4. Critical control failure

Attackers jailbroke Claude Code and used it to run most of a cyber espionage campaign

Developer
Anthropic
Model
Claude Code
When it happened
Not established
When it was disclosed
November 13, 2025
How well it is stood up
Confirmed by the primary source
What caused it
A person used the system to do it
Where it stands now
Mitigated

What happened

Anthropic reports that a threat actor tricked Claude Code into carrying out the bulk of an espionage campaign against about thirty organisations, succeeding against a small number of them. The attackers jailbroke the model by splitting the work into innocuous-looking tasks and telling it that it was doing defensive testing for a security firm. The tool then mapped target systems, wrote its own exploit code, harvested credentials, created backdoors and extracted private data. Anthropic says it detected the activity in mid-September 2025, banned the accounts over the following ten days, and published this account on 13 November 2025.

Our assessment

Actual
4 of 5Critical control failure
Potential
4 of 5Critical control failure

Serious loss of control, dangerous autonomous behaviour, or a credible path to severe harm. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.

This level rests on the developer's own account of its own system.

Why this level

  • Sustained harmful autonomous behaviour. Argues for level 4
  • Major compromise of an external system. Argues for level 4
  • A security boundary was crossed. Argues for level 3
  • An external system was affected. Argues for level 3
  • Significant data was exposed. Argues for level 3
  • A safeguard was bypassed. Argues for level 2
  • The system acted without authorisation. Argues for level 2
  • Sensitive data was reachable. Argues for a potential level of 3
  • The system acted autonomously. Argues for a potential level of 3
  • The behaviour repeated rather than stopping. Argues for a potential level of 3

Why this matters, in our words

This is a company describing its own product being turned into the main operator of an intrusion campaign rather than an adviser to one. The safeguards were not absent; they were talked around, by an attacker who never had to write the exploit code themselves.

What is established, and what is not

Confirmed

Reported, not confirmed

Nothing rests on a single report.

Checked, and did not happen

Nothing here was checked and ruled out.

Not confirmed

Nothing is outstanding.

Where this came from

The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.

Something here is wrong? Tell us. Send us a source we can open, and a person will read it.

Attackers jailbroke Claude Code and used it to run most of a cyber espionage campaign, Humanity & AI Safety Accord