Unit 42 CL-STA-1238 uses Cairn with Zhipu GLM and DeepSeek against semiconductor, defense, and civil-society targets
Palo Alto Networks Unit 42 (published Nov 12, 2026) tracks CL-STA-1238, assessed with moderate confidence as China-nexus intelligence collection. From August through September 2026, Chinese-speaking…
What happened
Palo Alto Networks Unit 42 (published Nov 12, 2026) tracks CL-STA-1238, assessed with moderate confidence as China-nexus intelligence collection. From August through September 2026, Chinese-speaking operators used the open-source Cairn framework (https://github.com/oritera/Cairn) for 25 operations against at least 19 organizations and confirmed unauthorized access or data retrieval at 10. They paired Cairn with Zhipu GLM 5.2 (13 operations), DeepSeek V4 Flash (8), and DeepSeek V4 Pro (4), using the higher-tier Pro model for repeats against targets that resisted Flash. Each operation loaded a skill pack named AIScan Runner Skills, which Unit 42 says is not in upstream Cairn. A worker system-prompt preamble framed every Reason and Explore phase as authorized security testing, CTF, assessment, vulnerability research, or code audit and forbade refusal. Each operation also wrote AUTHORIZATION.md treating task creation as a client-approved engagement. Neither model refused that framing. Operators supplied a one-line goal and a root domain, and sometimes prior intelligence such as VPN gateway addresses, group names, and shared group passwords. Cairn then mapped the target, broke the goal into three to seven stages, and looped until the model judged the goal met, options exhausted, or the operator stopped it. Individual operations ran from 20 minutes to more than 50 hours. Confirmed outcomes include weak-password spraying that yielded dozens of valid credentials and non-public directory data at an industry standards body, plus an unauthenticated cloud-storage write that overwrote a live standards-ballot document; a brute-forced production credential at a semiconductor company followed by unauthorized administrator accounts and a persistent API token; an unauthenticated account-creation bypass at a U.S. teachers' union that logged access to more than one million member records, roughly 31,000 CRM contacts, and staff password hashes; an open registration endpoint on a defense-policy identity platform exposing roughly 500 user records, including .mil and .gov accounts; and five further cases covering tens of thousands of content-management records, employee data at a semiconductor-lithography manufacturer, roughly 150,000 internal documents at an industrial-automation manufacturer, and student data at an education nonprofit. Targeting concentrated on semiconductor and advanced-manufacturing supply chain (seven organizations), defense and defense policy (three, including a space technology company, a defense-analytics vendor, and a policy think tank), and human rights and civil society (four, including a Canadian human-rights body, a U.S. teachers' union, a science-policy advocacy group, and an education nonprofit). Unit 42 assesses a single operator or small team. The exploited flaws were known classes: authentication bypasses, insecure direct object references, mass-assignment privilege escalation, weak and default credentials, exposed cloud APIs, and dated public CVEs. Infrastructure: Cairn hosting 154.44.31.4 (Hong Kong, AS979, NetLab Global) and egress and staging 82.29.129.54 (United States, AS142036, Hosteons Pte. Ltd.). Link cairn-norforge-2026-10 and cert-in-crafty-falcon-bfsi-2026-11.
CL-STA-1238 ran a customized Cairn fork so Zhipu GLM 5.2 and DeepSeek V4 Flash or Pro planned and executed intrusion tasks. A Chinese authorization preamble told the model never to refuse.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · Operator sets a one-line goal
The operator creates a Cairn task with a Chinese goal and a root domain, and sometimes VPN gateways, group names, and shared passwords.
Hunt: Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
Source for step 1 - 02 · GLM or DeepSeek plans the operation
GLM 5.2 or DeepSeek V4 Flash or Pro runs bootstrap, Reason, and Explore under an authorization preamble and the AIScan Runner Skills pack.
Hunt: An agent ingests external content or an untrusted session identifier before a tool action or configuration change outside the approved task.
Requires application instrumentation and a custom field mapping. Input exposure does not prove that the model followed instructions, executed a tool or bypassed approval. Avoid collecting sensitive prompt bodies unless authorized.
Source for step 2 - 03 · Autonomous exploit loop
The model maps the target into three to seven stages and loops from 20 minutes to more than 50 hours until the goal is met or the operator stops it.
Hunt: Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
Source for step 3 - 04 · Credentials, records, or admin accounts
Unit 42 confirmed unauthorized access or data retrieval at 10 of at least 19 organizations, including password spraying, cloud-storage overwrite, and minted administrator accounts.
Hunt: An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Source for step 4
Why it matters
Reported entry point: Operator-supplied root domain, sometimes with pre-gathered VPN gateways, group names, and shared passwords. Cairn then used authentication bypasses, weak or default credentials, insecure object references, and exposed cloud APIs. Reported impact: Unit 42 confirmed unauthorized access or data retrieval at 10 of at least 19 organizations, including password spraying, cloud-storage overwrite, and minted administrator accounts; reported targets include At least 19 organizations in semiconductor and advanced manufacturing, defense and defense policy, and human rights and civil society. Confirmed access or data retrieval at 10; applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.
What you can do
Protection & prevention
Treat agent-driven scanning as ordinary vulnerability volume, not a new exploit class. Remove weak and default credentials, close unauthenticated registration and cloud-storage writes, and patch known public-facing flaws. Block the two published IPs. Do not treat a same-/24 scan lead as this cluster without Unit 42's indicators.
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
01Operator sets a one-line goalUnexpected agent tool useCustom schema · Draft
The operator creates a Cairn task with a Chinese goal and a root domain, and sometimes VPN gateways, group names, and shared passwords.
What to look for
Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
Visibility: Defender-side logs where collected
Required logs
- Agent tool-call audit records with session / tool / destination
- Tool-definition and approval changes
- Endpoint process, file-access and network evidence where available
Coverage limit. Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Unexpected agent tool use
id: c709e384-0e11-479e-ab4d-3a06e2431e4b
status: experimental
description: Untrusted content or a changed tool definition precedes a file
read, command, or remote call outside the user's intended task.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- agent.tool.call
- agent.tool.definition.change
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("agent.tool.call", "agent.tool.definition.change")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("agent.tool.call", "agent.tool.definition.change")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Join input provenance, tool descriptions and calls by session ID and compare the action to the approved task.
- Inspect child processes and destinations; record whether execution was in-process, local, or through a remote SaaS connector.
02GLM or DeepSeek plans the operationUntrusted content enters an agent sessionCustom schema · Draft
GLM 5.2 or DeepSeek V4 Flash or Pro runs bootstrap, Reason, and Explore under an authorization preamble and the AIScan Runner Skills pack.
What to look for
An agent ingests external content or an untrusted session identifier before a tool action or configuration change outside the approved task.
Visibility: Application / agent audit records
Required logs
- Input provenance, source type and request/session identifier
- Captured tool responses or retrieved content where collection is approved
- Subsequent tool calls, configuration changes and approval decisions
Coverage limit. Requires application instrumentation and a custom field mapping. Input exposure does not prove that the model followed instructions, executed a tool or bypassed approval. Avoid collecting sensitive prompt bodies unless authorized.
Custom-schema candidate for input exposure only. Map agent.input.ingest and agent.session.resume to your application request and session logs. CorrelationId must link subsequent actions. EventType values are proposed normalization names, not native vendor events.
Sigma
title: Hunt - Untrusted content enters an agent session
id: 2d89d7ae-9d44-4dc6-a95b-f9c8de7b8352
status: experimental
description: An agent ingests external content or an untrusted session
identifier before a tool action or configuration change outside the approved
task.
author: MagicSword OpenAttacks catalog
date: 2026-11-04
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- agent.input.ingest
- agent.session.resume
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("agent.input.ingest", "agent.session.resume")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("agent.input.ingest", "agent.session.resume")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Join the ingested input to later actions by session or request ID; preserve the original content as evidence.
- Compare the resulting action with the approved task and baseline. Receiving suspicious text alone is not successful injection.
03Autonomous exploit loopWeb exploitation → host activityCustom schema · Draft
The model maps the target into three to seven stages and loops from 20 minutes to more than 50 hours until the goal is met or the operator stops it.
What to look for
Repeated exploit or upload requests are followed by an unexpected server process, file, or outbound connection.
Visibility: Defender-side logs where collected
Required logs
- Reverse-proxy / WAF request logs
- Server process and file events
- Outbound DNS / proxy records
Coverage limit. A scan or high request rate alone does not prove compromise or AI use. Host telemetry is needed to confirm execution.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Web exploitation → host activity
id: 04d900b5-0c04-46f2-a13a-91f5574fae98
status: experimental
description: Repeated exploit or upload requests are followed by an unexpected
server process, file, or outbound connection.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- web.exploit_candidate
- web.upload
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("web.exploit_candidate", "web.upload")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("web.exploit_candidate", "web.upload")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Join requests to the affected host and process tree by time and request ID.
- Inspect uploaded files and server-spawned shells; distinguish authorized testing from exploitation.
04Credentials, records, or admin accountsSensitive store access → credential useCustom schema · Draft
Unit 42 confirmed unauthorized access or data retrieval at 10 of at least 19 organizations, including password spraying, cloud-storage overwrite, and minted administrator accounts.
What to look for
An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Visibility: Defender-side logs where collected
Required logs
- File-read / API access telemetry for relevant secret stores
- Process identity and command lines
- Identity, token and outbound-network audit logs
Coverage limit. Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Sensitive store access → credential use
id: 46c46c62-2d83-4198-a8bf-d6637094527b
status: experimental
description: An unexpected process or tool accesses credential stores and is
followed by token use or outbound transfer inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- secret.read
- credential.store.read
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("secret.read", "credential.store.read")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("secret.read", "credential.store.read")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Identify the actor, process and exact store touched, then pivot to token use from new devices or infrastructure.
- Correlate reads with egress and rotate affected credentials after confirming exposure.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
- Offensive frameworks
- Cairn
- Initial access
- Operator-supplied root domain, sometimes with pre-gathered VPN gateways, group names, and shared passwords. Cairn then used authentication bypasses, weak or default credentials, insecure object references, and exposed cloud APIs.
Tooling as reported
AI products, models and artifacts
Targets and reported impact
- Targets / sectors
- At least 19 organizations in semiconductor and advanced manufacturing, defense and defense policy, and human rights and civil society. Confirmed access or data retrieval at 10.
- Reported scale / exposure
- 25 operations, at least 19 organizations, confirmed unauthorized access or data retrieval at 10. Thirteen operations on GLM 5.2, eight on DeepSeek V4 Flash, four on DeepSeek V4 Pro. One organization exceeded one million member records. Operations lasted from 20 minutes to more than 50 hours.
- Target geography
- Multiple regions
Named targets include U.S. defense-policy organizations, a U.S. teachers' union, and a Canadian human-rights body. Other organizations' countries were not stated. Hong Kong and the U.S. egress host are infrastructure, not victim regions, so the entry uses Multiple regions.
Reported attribution
CL-STA-1238. Unit 42 assesses moderate confidence of China-nexus intelligence collection from Chinese tasking and authorization files, exclusive use of Zhipu GLM and DeepSeek, and the target set.
Structured attribution
- Actor
- CL-STA-1238
- Country
- China
- Motivation
- nation-state
- Attributed by
- Palo Alto Networks Unit 42
- Attribution confidence
- medium
Detection rules
- Cairn web outcomes have no single host ruleGUIDANCE
Unit 42 describes weak-password spraying, unauthenticated cloud-storage writes, account-creation bypasses, and minted administrator accounts on unnamed application stacks. No Sigma, Splunk, or Elastic rule names Cairn, AIScan Runner Skills, or those application flaws. Hunt the published IPs 154.44.31.4 and 82.29.129.54, unexpected administrator accounts and API tokens, and unauthenticated writes to standards or directory data. A same-/24 panel lead is not an indicator from this report.
Activity timeline
- First seen
- 2026-08
- Last updated
- 2026-11-12
Updates
- 2026-09 — Palo Alto Networks Unit 42
CL-STA-1238 completes 25 Cairn operations, August through September 2026, with confirmed access or data retrieval at 10 organizations
- 2026-11-12 — Palo Alto Networks Unit 42
Unit 42 publishes the CL-STA-1238 report, including GLM and DeepSeek model counts, the AIScan Runner Skills pack, and IPs 154.44.31.4 and 82.29.129.54. A same-/24 address, 154.44.31.104, is an unconfirmed Censys panel lead and is not an IOC.
Linked tools
- Cairn — agentic-offensive-framework
Source defensive notes
Treat agent-driven scanning as ordinary vulnerability volume, not a new exploit class. Remove weak and default credentials, close unauthenticated registration and cloud-storage writes, and patch known public-facing flaws. Block the two published IPs. Do not treat a same-/24 scan lead as this cluster without Unit 42's indicators.
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
Operators drove Cairn with Zhipu GLM 5.2 and DeepSeek V4 Flash and Pro Source
A Chinese preamble and AUTHORIZATION.md told the models the work was authorized and never to refuse Source
Each operation loaded the AIScan Runner Skills pack for scanning and exploitation Source
Confirmed access used authentication bypasses, weak credentials, and exposed cloud APIs on public-facing systems Source
Indicators of compromise
domains
ips
154.44.31.482.29.129.54
hashes
urls
Sources & research credit
2 sourcesResearch by Unit 42 · Palo Alto Networks Unit 42
- Attackers Use Autonomous AI to Target Semiconductor, Defense and Civil Society Sectors unit42.paloaltonetworks.com
- Cairn github.com
Counts, models, the AIScan Runner Skills pack, the authorization preamble, the confirmed outcomes, and the two IPs are from the Unit 42 article. 154.44.31.104 was described as another live Cairn panel in the same /24 as the controller 154.44.31.4, attributed to a Censys observation. It is not in the Unit 42 indicator list, and no public Censys report naming that address was available to confirm it. It is an unconfirmed lead only and is not an IOC. Cairn is open source, so an exposed panel is not by itself this cluster. Link cairn-norforge-2026-10, the cairn tool page, and cert-in-crafty-falcon-bfsi-2026-11. No victim organization names are repeated beyond the sector descriptions Unit 42 published.
Record & downloads
- Source record name
- Unit 42 CL-STA-1238 uses Cairn with Zhipu GLM and DeepSeek against semiconductor, defense, and civil-society targets
- Entry ID
- unit42-cairn-cl-sta-1238-2026-11
- Catalog review
- November 15, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed