Barracuda links 44-hour cloud breach to leftover key and ARTEX
November 17: Cyber Security News reports builds printed encoded secrets into job logs, wallet searches found none, and incomplete logging left XDR credential access unruled-out.
Barracuda says an unnamed attacker used a leftover vendor cloud key and ARTEX for about 44 hours across roughly 10 accounts.
Barracuda said attackers entered its cloud on November 1–2 with a cloud access key left active after an AI vendor project ended, and associated the activity with the open-source ARTEX pentesting framework. The intrusion lasted about 44 hours across roughly 10 accounts, reached analytics, source code and Kubernetes, searched for cryptocurrency secrets, and attempted a host-mounting container and a new administrator identity that was blocked. Barracuda believes the key was taken in October from the vendor’s GitHub configuration file and has not named a group. It found no evidence Barracuda XDR customer credentials were stolen; later reporting said incomplete logging left that access unruled-out. Separately, CrowdStrike links China-nexus VAPOR PANDA to ARTEX activity against more than 200 organizations in at least 14 countries from October 17, with post-compromise confirmed at nine. Microsoft attributes ARTEX-driven sign-in attempts against more than 2,250 Microsoft 365 tenants to Storm-0940.
- Activity ran from 04:33 UTC November 1 to 23:31 UTC November 2.
- Barracuda disclosed the incident on November 10 and blocked a new admin identity.
- ARTEX was published on GitHub in July 2026 and withdrawn in October.
- CrowdStrike confirmed post-compromise activity at nine of more than 200 organizations.
- Microsoft said successful Storm-0940 authentication did not establish data access.
- Censys saw roughly 1,500 exposed Artex consoles in early November.
Timeline
dated events in the reporting · oldest first- Oct 17, 2026CrowdStrike dates VAPOR PANDA ARTEX activity from this day · GBHackers
- Nov 1, 2026Barracuda cloud access began at 04:33 UTC · GBHackers
- Nov 2, 2026Barracuda intrusion ended at 23:31 UTC · GBHackers
- Nov 4, 2026Barracuda discovered the attacker’s presence · BleepingComputer
- Nov 10, 2026Barracuda disclosed the cloud incident · GBHackers
What each outlet adds
beyond the shared facts- Palo Alto Unit 42Counted 609 ARTEX and 1,323 CyberStrikeAI internet-facing hosts in October.
- Elastic Security LabsFive frameworks exceed 60,000 stars; bursts every 2–25 seconds.
- Cisco TalosFound more than 700 reachable PentAGI instances.
- SecurityWeekTalos also links Storm-3358; Censys saw about 1,500 Artex consoles.
- Cyber Security NewsJob logs printed encoded secrets; XDR access not ruled out.
- Vendors
- BarracudaConnectWise
- Products
- ARTEXPentAGIHexStrike AIHephaestusMicrosoft 365ConnectWiseBarracuda XDRManaged XDR CloudAzure Key VaultCyberStrikeAICairn
- Threat actors
- Vapor PandaStorm-0940Storm-3358VAPOR PANDA
- Malware
- ArtexVolta InfostealerVShellGoPhishAdaptixC2ARTEXCyberStrikeAICairnPentAGIHexStrikeHephaestusMimikatz
- Victims
- BarracudaConnectWiseRailway
- Organizations
- FBISentinelOneCisco TalosAmazonCensysCrowdStrikeMicrosoftGoogle Threat Intelligence GroupMandiantUnit 42Railway
- Countries
- ChinaSouth Korea
Coverage
oldest first · one row per article · UTCAttackers use ARTEX and AI red-team tools in intrusions
Unit 42 counted 609 internet-facing ARTEX hosts and 1,323 running CyberStrikeAI as of October 2026.
Five agentic offensive frameworks seen in real intrusions
GTIG and Mandiant saw ARTEX, Cairn, HexStrike, and PentAGI in incidents; Microsoft links ARTEX to Storm-0940.
Talos tracks criminal and China-nexus use of ARTEX pentest framework
CrowdStrike says China-nexus VAPOR PANDA used ARTEX against more than 200 organizations in at least 14 countries.
Talos finds 700 internet-reachable PentAGI instances as AI attack tools spread
The count covers reachable deployments, not confirmed abuse; named operators have used the separate ARTEX framework against hundreds of organizations.
Barracuda breached as Chinese groups adopt Artex AI attack framework
Between November 1 and 2 an attacker used a cloud key to reach about 10 accounts, steal secrets, and leave a Kubernetes backdoor.
Barracuda ties cloud breach to stolen key and ARTEX
A leftover vendor cloud key was used for about 44 hours across roughly 10 accounts; XDR credential theft is unproven.
Barracuda ties 44-hour cloud intrusion to leftover vendor key
Attackers chained stolen cloud secrets into Kubernetes and source code while hunting wallets and reusable credentials.
Stolen AI vendor key reached about 10 Barracuda cloud accounts
Over November 1–2 the attacker moved from cloud secrets into analytics, source code, and Kubernetes; creating an admin identity was blocked.