Overview
Between August and September 2026, a Chinese-speaking threat cluster designated CL-STA-1238 conducted 25 autonomous offensive cyber operations against at least 19 organizations using the open-source AI penetration testing framework Cairn. The campaign successfully achieved unauthorized access or data retrieval at 10 targets, spanning advanced semiconductor manufacturing, U.S. defense policy institutions, and civil society groups. Palo Alto Unit 42 assesses with moderate confidence that the activity constitutes China-nexus intelligence collection — marking one of the most operationally significant documented deployments of autonomous AI agents for state-aligned offensive operations.
Technical Analysis
Cairn is a publicly available penetration testing framework in which an AI model drives each “agent worker.” Agents coordinate via a shared blackboard architecture: they read the current operational state, write findings back as a fact-intent graph, and queue subsequent actions as intents. Confirmed findings are stored as immutable facts, ensuring continuity across the operation. Human operators can inject “hints” at any point to steer agent behavior without fully taking over.
The threat actors ran a customized Cairn fork from a Hong Kong-hosted server (154.44.31[.]4, AS979, NetLab Global) and routed attack egress through a U.S.-based staging node (82.29.129[.]54, AS142036, Hosteons Pte. Ltd.). The AI backbone was provided by two Chinese-developed models: Zhipu GLM and DeepSeek. Operators supplied each operation with a target and a goal; Cairn then planned, executed, and logged results autonomously.
Successful outcomes across the 10 breached organizations included:
- Accessing dozens of valid credentials
- Mass exposure of personal data (exceeding one million records at one organization)
- Retrieval of military and government personnel identities
- Creation of persistent administrator accounts in a production system
- Modification of a live industry standards-ballot document
The framework’s blackboard architecture is particularly notable from a defensive standpoint: it enables stateful, multi-step attack chains that persist across agent sessions, making detection through single-session anomaly analysis insufficient.
Framework Mapping
MITRE ATLAS:
- AML.T0103 (Deploy AI Agent): Core operational mechanic — Cairn agents autonomously executed attack phases end-to-end.
- AML.T0086 (Exfiltration via AI Agent Tool Invocation): Credentials and personal data were retrieved through agent-driven tool calls.
- AML.T0083 (Credentials from AI Agent Configuration): Valid credentials were harvested as part of the autonomous operation.
- AML.T0012 (Valid Accounts): Acquired credentials were leveraged for persistent access and privilege escalation.
OWASP LLM Top 10:
- LLM08 (Excessive Agency): The defining risk — AI agents operated with broad autonomy, executing destructive and exfiltration actions without human checkpoints.
- LLM06 (Sensitive Information Disclosure): Personal data, government identities, and credentials were exfiltrated at scale.
Impact Assessment
The breadth and severity of confirmed outcomes place this campaign in a critical threat tier. The modification of a live industry standards document introduces a novel integrity risk beyond traditional data theft. The exposure of over one million personal records at a single organization carries significant regulatory and reputational consequences. The use of open-source, commercially available AI tooling lowers the barrier for similar operations by other actors.
Mitigation & Recommendations
- Block known infrastructure: Deny traffic to and from
154.44.31[.]4and82.29.129[.]54at perimeter controls. - Audit privileged accounts: Immediately review production systems for unauthorized administrator accounts created after August 2026.
- Implement PAM/IAM controls: Deploy privileged access management to detect lateral movement and credential misuse consistent with autonomous agent behavior.
- Monitor for Cairn indicators: Review endpoint and network telemetry for Cairn framework signatures, including blackboard-style stateful API call patterns.
- Restrict AI model API access: Apply least-privilege policies to any internal or third-party AI model API integrations to limit agent tool scope.
- Conduct AI security assessments: Engage offensive security teams to validate exposure across agentic attack paths before adversaries do.