Get the Zoom link
Cloud Security Office Hours Banner

VAPOR PANDA / ARTEX Campaign 2026

Step-by-step kill chain mapped to MITRE ATT&CK Cloud, sourced from official post-mortems and primary technical analyses.

October 2026 Critical AI-Driven / Hybrid Cloud

VAPOR PANDA / ARTEX - An Operator Steering an Agent Graph → 200+ Organizations in 11 Days → SAML and XXE Chains → A Metadata Role Over Thousands of Instances → BLOODALCHEMY at Two Ministries

CrowdStrike OverWatch saw this campaign begin on October 17, 2026. Over the next 11 days, it reports, the China-nexus adversary VAPOR PANDA used the ARTEX agentic framework against more than 200 organizations in at least 14 countries, including foreign ministries, US semiconductor, defense and think tank organizations, and telecommunications providers. CrowdStrike Intelligence confirmed post-exploitation at nine organizations, and says password spraying and credential scanning hit at least 12 more. The headline figure of about 140 compromised targets comes from CrowdStrike's comments to CyberScoop, where about 70% of targets were either confirmed or showed moderate-confidence evidence of intrusion. CrowdStrike's report and that interview measure different things, so this page uses nine for confirmed intrusions. CrowdStrike states that this campaign is separate from the ARTEX activity Microsoft attributes to Storm-0940, and that VAPOR PANDA has not previously been seen using AI-driven intrusion tooling. Adam Meyers of CrowdStrike told CyberScoop that the attacks showed nothing new in technique. What changed is the rate: Meyers puts typical hands-on activity at up to about 40 commands an hour, and said ARTEX could exceed 1,500.

200+ organizations targeted in at least 14 countries over 11 days
9 organizations with confirmed post-exploitation, per CrowdStrike Intelligence
1,500+ commands/hour possible with ARTEX, per CrowdStrike, against up to 40 hands-on
Threat actor: VAPOR PANDA, China-nexus, per CrowdStrike
📄 CrowdStrike - VAPOR PANDA uses ARTEX to scale a global campaign ↗ 📄 CyberScoop - Interview reporting and the 140 figure ↗
🧰 Resource Development: Agents With a Human at the Decision Points
01
ARTEX split each intrusion among planner and worker agents, and a human operator stepped in to steer
T1588.007 - Obtain Capabilities: Artificial Intelligence

ARTEX coordinates a main agent with planner and worker agents over a shared graph of facts, findings and goals. CrowdStrike says the operation ran primarily on the DeepSeek model, with a second, subscription-based commercial model it could not confirm. One intrusion's planning agents consumed on the order of 1.4 billion input tokens.

This was not an unattended system. Recovered transcripts show Chinese-language instructions labeled as human input, directing agents to write web shells, extract domain administrator passwords and inventory endpoint sensor coverage. CrowdStrike says the operator intervened only to steer at decision points, and that this breadth likely enables a single operator to apply more techniques against more targets at once.

Structure: main agent, planner and worker agents, shared graph
Models: primarily DeepSeek, plus a second unconfirmed commercial model
Scale marker: about 1.4 billion input tokens for one intrusion's planning agents
Human role: steering at decision points, in Chinese-language instructions
ARTEXDeepSeekHuman in the LoopT1588.007
⚡ Initial Access: Public Applications and Valid Accounts
02
Agents exploited public-facing applications, in one case chaining an unsigned SAML assertion with an XXE flaw
T1190 - Exploit Public-Facing Application

CrowdStrike describes exploitation of public-facing applications and misuse of valid accounts, with agents pursuing several attack paths at once across web applications, cloud services, container environments, Active Directory, and mail and VPN infrastructure. When one path failed they switched to another.

One case chained an unsigned Security Assertion Markup Language assertion with an XML external entity flaw. CyberScoop reports requests as often as every 10 seconds, with multiple paths running concurrently.

Entry: public-facing applications, valid accounts
Example chain: unsigned SAML assertion plus XXE
Tempo: requests as often as every 10 seconds, per CyberScoop
Also seen: password spraying and credential scanning at 12 or more further organizations
SAMLXXEParallel PathsT1190T1110.003
🔑 Credential Access: Keys Nobody Rotated
03
At a Greek government entity, the operator supplied directory export keys and the agent forged an administrator token
T1606 - Forge Web Credentials

Against a Greek government entity, the operator gave the agent a 2022 directory export containing authentication keys that had likely not been rotated since. The agent used them to forge an administrator token, then used VPN configurations and a VPN client key, which the operator described as coming from a May 2024 email leak, to reach the internal network.

The detail worth noting is where the keys came from. A person supplied the material, and the agent did the mechanical work of turning it into a foothold.

Supplied by the operator: a 2022 directory export, keys likely not rotated since
Forged: an administrator token
Reached: the internal network, with VPN configurations and a client key the operator said came from a leak
Token ForgeryUnrotated KeysVPNT1606T1133
🔑 Credential Access: The Metadata Service
04
At a US pharmaceutical organization, the metadata service yielded a role able to command thousands of instances
T1552.005 - Cloud Instance Metadata API

This is the most directly cloud-focused step in the report. The agent queried the cloud Instance Metadata Service at a US pharmaceutical organization and obtained a role capable of issuing administration commands to thousands of instances, then escalated to an enterprise administrator account.

Cloud security teams have known this path for years. A workload's instance role is reachable by anything running on the workload, and a role that can command a fleet turns one compromised host into all of them.

Queried: cloud Instance Metadata Service
Obtained: a role able to issue administration commands to thousands of instances
Then: escalation to an enterprise administrator account
Control: IMDSv2, plus instance roles scoped to one workload
IMDSInstance RoleBlast RadiusT1552.005T1651
⬆️ Privilege Escalation: Containers and Active Directory
05
An unauthenticated orchestration service gave root in production, and LAPS and delegation abuse worked on the domain side
T1609 - Container Administration Command

A second pharmaceutical intrusion abused an unauthenticated orchestration service to gain root access in a production container environment. On the Windows side, reported actions include reading LAPS passwords and using resource-based constrained delegation to impersonate a privileged account.

Neither technique is rare. Seeing both in one campaign shows how many kinds of environment this operation covered with agents doing the work.

Containers: unauthenticated orchestration service, root in production
Active Directory: LAPS passwords read, resource-based constrained delegation
Pattern: the same operator working cloud, container and domain targets
Container OrchestrationLAPSRBCDT1609T1078.002
🥸 Stealth: Finding the Hosts Nobody Watches
06
The operator told agents to find Windows machines without a Falcon sensor, then routed traffic through Tor and tunnels
T1518.001 - Software Discovery: Security Software Discovery

At a global pharmaceutical organization, the operator instructed the agents to find Windows machines in the domain with no Falcon sensor, judging by process lists and folder contents, so follow-on activity could concentrate on unprotected hosts. Coverage gaps became a target list.

Traffic ran through Tor, SOCKS proxies and a compromised relay, with tunneling over Chisel and SoftEther.

Instruction: find domain hosts without a sensor, using tasklist and folder listings
Purpose: concentrate follow-on activity on unmonitored machines
Network: Tor, SOCKS proxies, a compromised relay, Chisel, SoftEther
Sensor GapsTorChiselSoftEtherT1518.001T1090.003
🔐 Persistence and Collection: BLOODALCHEMY and Mail
07
BLOODALCHEMY went onto two ministries by side-loading a renamed binary, and mailboxes were read
T1574.001 - Hijack Execution Flow: DLL

CrowdStrike reports the BLOODALCHEMY backdoor, first publicly documented in October 2023, at a Middle East interior ministry and a Latin American foreign ministry. The adversary renamed a legitimate GameHook binary to svchost.exe and used it to load a malicious DLL, which decrypted the payload.

Mailboxes on a compromised mail server were also read. That fits an actor CrowdStrike says has mainly pursued long-term access to government, think tank, energy and extractive organizations since 2021. The agents sped up the path to that goal, and the goal itself stayed the same.

Implant: BLOODALCHEMY, at two government ministries
Loader: legitimate GameHook binary renamed svchost.exe, malicious DLL
Collection: mailboxes read on a compromised mail server
Status: CyberScoop reported the campaign as active on October 30
BLOODALCHEMYDLL Side-LoadingMailbox AccessT1574.001T1114.002

🛡 How to Defend Against This Chain

Rotate keys after any suspected exposure, on a schedule you can prove. The Greek government step ran on keys likely not rotated since a 2022 export, and a VPN client key the operator tied to a 2024 leak finished the job. Agents make old, half-forgotten secrets cheap to use. Keep an inventory of long-lived signing and export keys, and rotate them when exposure is suspected as well as on a calendar.
Require IMDSv2 and scope instance roles to one workload. CrowdStrike recommends IMDSv2 directly. The larger problem in this case was a role able to command thousands of instances sitting on a single host. Fleet administration should go through a separate, tightly held identity, reachable only from a management path.
Enforce SAML signature validation everywhere. An unsigned assertion should never be accepted. Test your service providers for it, and patch internet-facing appliances, since those are where the first request lands.
Close the sensor gaps an attacker can enumerate. The operator's own instruction shows what coverage gaps are worth to an attacker. Run endpoint detection on servers that are not reachable from the internet, and measure coverage by host, because the unmonitored machines are the ones this operator went looking for.
Hunt for ARTEX markers and for machine tempo. CrowdStrike suggests hunting command lines containing artx or artex strings, artx-prefixed cloud roles, and the C:\ProgramData\artx5v\ directory. Indicators like these change quickly. A more durable signal is tempo: command rates far above the 40 an hour CrowdStrike gives for hands-on work are measurable in any environment.
Lock down orchestration services. An unauthenticated orchestration endpoint gave root in production. Require authentication on every container management API, keep those endpoints off shared networks, and scan for exposed ones regularly.

Related defense topics