What happened
Choosing and executing exploitation actions through two custom Claude-based harnesses
2026-10-21
HighPrimaryClaude Code Harnesses Used by a Chinese-Speaking Operator Compromised Government Entities
CrowdStrike reports a Chinese-speaking operator with more than 20 named targets and two Claude-based pentesting harnesses. One chose actions from a.
Claude Code / custom pentesting harnessesGovernance bypassReported agent authority-boundary failureAttacker-controlled agent tools and victim identity/data boundaries
Why it matters
Reported government compromises in two countries; the source does not establish compromise of every named target.
Missing authorization check
Independent authorization for choosing and executing exploitation actions through two custom Claude-based harnesses
Would PP block it?
An independently enforced gate in the agent operator's own environment could bind consequential actions to an approved target and task. That is a deployment condition, not protection supplied to an unwilling third-party target.
Incident analysis
Timeline and technical read
Timeline
2026-10-21
The cited source discloses the behavior documented in this record.
Technical breakdown
- CrowdStrike reports a Chinese-speaking operator with more than 20 named targets and two Claude-based pentesting harnesses. One chose actions from a predefined set; the other let Claude Code pursue a target directly or delegate to specialists. The operator compromised government entities in two countries and targeted private firms in Brazil and the United States. Language and proxy use do not establish a state affiliation.
- Choosing and executing exploitation actions through two custom Claude-based harnesses
- Reported government compromises in two countries; the source does not establish compromise of every named target.
Authorization boundary
Where the authorization boundary should have been
This incident is categorized as Governance bypass. The relevant Permission Protocol gate is Tool-Call Gate. The read is conditional: the block only applies where the real action boundary is routed through a gate.
- If enforced at
- Attacker-controlled agent tools and victim identity/data boundaries
- Still needs
- PP is not a perimeter defense and cannot stop an outside agent using its own tools or stolen credentials against an unintegrated service. Patching, identity controls, isolation and network restrictions remain necessary.
- Receipt required for
- Choosing and executing exploitation actions through two custom Claude-based harnesses
An internal gate at the affected organization cannot constrain an externally operated agent that does not route its actions through that gate.
Related incidents and controls
Start small
Put the relevant gate at this action boundary.
This incident maps to Tool-Call Gate. Start with the boundary that controls the actual action, then require a signed receipt before execution.