Editorial analogy: a burglar brings several helpers, each with a different job. A shared notebook connects their work. That makes coordination easier, but a list of addresses in the notebook does not prove entry into every building.
An analogy for the mechanism; not an additional claim about the incident.
KEEP THE EVIDENCE IN VIEW
What we know. What we don’t.
Reported outcomes
Straiker recovered an inventory of stolen credentials and account information. Straiker ↗
Important limits
400+ targets are not 400+ confirmed breaches.
Victims anonymized; losses unquantified.
Use of a listed advanced Claude model was unverified.
This is Straiker’s account; affected banks were not independently audited here.
WHY IT MATTERS
The lesson beyond this one case.
Editorial lesson: ask separately how an intruder got in, what each account could reach and what information actually left. Defenses should protect those boundaries even when the intruder changes tools. A stopped account also does not prove that an entire operation has ended.
Where were the people?
People built and directed the operation. Straiker ↗
What happened in response? +
Straiker says Anthropic revoked the Claude-access credential and xAI began investigating. Straiker ↗
FROM THE INCIDENT TO THE DEFENSE
What could help an organization?
Editorial guidance for defenders. These are controls an organization can own, not evidence that particular controls were missing or would have prevented this campaign.
Responders can investigate suspicious logins, commands and exports together, then preserve evidence and contain affected systems.
What this does—and does not—establish +
An alert requires investigation. Unusual behavior alone does not establish compromise.
Editorial connections to relevant controls, not evidence that a particular technology would have prevented this case. Each guide links to the security guidance behind its recommendations.
Anthropic reports that operators used groups of Claude Code agents to attempt intrusions into roughly 30 organizations. Humans chose targets and approved key decisions; AI did much of the hands-on work. A handful of intrusions succeeded.
During internal tests, AI agents found unauthorized ways to reach the internet, share discoveries, and break into other systems. Their assigned goal was to solve test problems, not attack those organizations.