Barracuda links 44-hour cloud breach to leftover vendor key
First merged summary.
Barracuda says a leftover AI vendor cloud key was used for about 44 hours across roughly 10 accounts; XDR theft is unconfirmed.
Barracuda said attackers entered its cloud environment on November 1–2, 2026, using a cloud access key left active after an AI vendor’s project ended. The company believes the key was taken in October from a configuration file in that vendor’s GitHub repository. Across roughly 10 accounts, the attacker reached analytics, source code and Kubernetes, hunted wallet secrets, and tried to persist with a host-mounted container. Barracuda links the method to the open-source ARTEX framework but has not named the attacker. BleepingComputer reports no evidence that XDR integration credentials were taken; Cyber Security News says incomplete logging left that access unruled-out.
- Activity ran from 04:33 UTC November 1 to 23:31 UTC November 2.
- Barracuda discovered the intrusion on November 4 and disclosed it on November 10.
- No cryptocurrency wallet material was found on the searched systems.
- Creating a new administrative cloud identity was blocked.
- Notified customers were told to recreate Barracuda XDR integration credentials.
- Customers who were not contacted were told they did not need to act.
Timeline
dated events in the reporting · oldest first- Nov 1, 2026Cloud access begins at 04:33 UTC · Cyber Security News
- Nov 2, 2026Last recorded activity at 23:31 UTC · GBHackers
- Nov 4, 2026Barracuda finds access and removes a container · Cyber Security News
- Nov 10, 2026Barracuda discloses the cloud incident · GBHackers
What each outlet adds
beyond the shared facts- BleepingComputerSays XDR credential theft is unproven; likens case to Railway.
- Cyber Security NewsIncomplete logging cannot rule out XDR credential access; no wallets found.
- GBHackersGives the November 10 disclosure date and named indicators.
- SecurityWeekBarracuda has not named the group behind the intrusion.
- Vendors
- BarracudaConnectWise
- Threat actors
- Vapor PandaStorm-0940Storm-3358VAPOR PANDA
- Victims
- BarracudaConnectWiseRailway
- Countries
- ChinaSouth Korea
- AI models
- DeepSeek v4.1-flashGLM-5.3Grok 4.6
Coverage
oldest first · one row per article · UTCTalos 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.
Exposed AI vendor key reached about 10 Barracuda cloud accounts
Over November 1–2 the intruder read cloud secrets, source tokens, and Kubernetes credentials; XDR customer access was not confirmed.