- Unit 42 says a likely single operator or small team used the open-source Cairn framework in 25 operations against at least 19 organizations.
- Unit 42 confirmed unauthorized access or data retrieval at 10 of them, through known weaknesses such as weak passwords and open endpoints.
- Unit 42 says identity hygiene, attack-surface reduction and patching still work. Leaders should check how fast they find and close basic gaps.
The limit that just moved
For years, an attacker's reach was set by working hours. One person can only probe so many targets at once. Unit 42, the research arm of Palo Alto Networks, describes a campaign where that limit appears to have gone.
In August and September 2026, Chinese-speaking attackers used Cairn, a publicly available AI tool for penetration testing. That is security testing that imitates an attacker. Unit 42 says they ran 25 operations against at least 19 organizations.
Unit 42 judges the group was likely one operator or a small team. Its attempts on all 19 ran side by side over about two weeks.
The lesson here is that autonomy changes the economics of attack more than the sophistication. A small team can now cover a target list that once needed a larger one.
What the researchers found
Unit 42 tracks the activity as CL-STA-1238. It assesses with moderate confidence that this is China-nexus intelligence collection. Its evidence is Chinese-language task files, the use of Chinese AI models, and a target list that fits established Chinese state intelligence priorities.
Targets fell into three groups. Seven were in the semiconductor and advanced-manufacturing supply chain. Three were in defense and defense policy, including a space technology company and a policy think tank. Four were human rights and civil society groups, including a Canadian human-rights body and a U.S. teachers' union.
Unit 42 says the attackers got in, or pulled data out, at 10 of the 19. At one, Cairn's own log shows access to over a million member records. It also shows about 31,000 contacts from a customer database.
At a defense-policy program, an open registration endpoint exposed roughly 500 user records. Some used .mil and .gov domains. At an industry standards body, attackers overwrote a live ballot document.
On a partner-integration application, the attackers guessed a production credential that worked across several accounts. They then added their own administrator accounts and left behind a lasting API token.
How the tool works
Each Cairn worker is run by an AI model. Workers share a "blackboard". This is a common record of confirmed findings and queued next steps. Human operators can add hints at any time.
The attackers gave Cairn a one-line goal and a company's root domain. Cairn mapped the target and split the goal into small tasks. Unit 42 says the model drew up a different plan for each target, with three to seven stages.
The work runs as a loop with two steps. First the model reviews everything found so far and chooses its next move. Then it takes a single action, and Cairn logs the result as a new finding.
The loop repeats until the model decides it is done, runs out of ideas, or the attacker stops it. Runs lasted from 20 minutes to over 50 hours. The attackers set no time cap.
Cairn works with any model. These attackers chose Chinese ones: GLM 5.2 from Zhipu, and DeepSeek V4 in its Flash and Pro tiers. They seem to have compared them. When Flash failed on a target, they retried with the stronger Pro.
Cairn told the model never to refuse, and an authorization claim went unchallenged
Cairn's stock prompts already tell the model never to refuse a task. The attackers added their own Chinese-language preamble. It said the engagement was authorized and forbade refusal.
Each run also produced a file named AUTHORIZATION.md. It declared the work approved by a client. The only approval was that the attackers themselves had created the task. Unit 42 says neither GLM nor DeepSeek refused this framing.
Unit 42 calls the pretext trivial. This shows only that these two models went along with it. The no-refusal instructions were also in place. We cannot say the authorization claim alone did the work.
Unit 42 describes easily accessible open models as having weak guardrails against offensive cyber actions. Defenders should plan for attackers having such models.
The flaws were ordinary
Unit 42 stresses that the vulnerabilities were known. They included weak-password spraying and a production credential reused across accounts. They also included an unauthenticated write to cloud storage. Another was an account-creation bypass on a content management system.
In one case, the attackers brought VPN gateway addresses and shared group passwords gathered beforehand.
Unit 42's takeaway is that autonomous AI widens the volume and coverage of exploitation. It does not make the exploits more complex. It says identity hygiene, attack-surface reduction and patching remain effective.
Unit 42 also assesses that such campaigns will grow more common. That is its forecast, not a measured trend. This is one campaign reported by one vendor, and Unit 42 sells related services. The findings are still specific and checkable.
Questions for your security team
Ask how many internet-facing logins allow weak or reused passwords. Ask whether anyone has tested them with password spraying lately. Ask whether any registration or account-creation endpoint is open that should be closed.
Ask how long a new exposure stays open before you find it. Unit 42 says this tool can work many targets at once. A gap does not have to wait for an operator's attention. Ask whether cloud storage and shared VPN credentials have been reviewed.
Ask which partner and vendor integrations hold production credentials that work across several accounts. Finally, ask whether your testing runs continuously or once a year.
The attackers' bottleneck was time. Yours is attention to basics, and the two now meet.
Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: Palo Alto Networks Unit 42.





