Exposed AI vendor key reached about 10 Barracuda cloud accounts
Original title: Hackers Exploit Exposed AI Vendor Key to Breach 10 Barracuda Cloud Accounts in 44 Hours
Over November 1–2 the intruder read cloud secrets, source tokens, and Kubernetes credentials; XDR customer access was not confirmed.
Barracuda said a cloud key left active with a third-party AI vendor was exposed after that vendor’s development environment was compromised in October. From November 1 to November 2, 2026, attackers reached about 10 cloud accounts, harvested stored secrets, entered analytics and Kubernetes systems, and triggered builds that printed secrets into logs. Barracuda associated the activity with the ARTEX penetration-testing framework but did not name the attacker. Contacted customers were told to recreate integration credentials.
Unconfirmed: Incomplete logging left open whether Barracuda XDR customer-telemetry credentials were accessed; the AI supplier is unnamed.
- The first recorded API call was at 04:33 UTC on November 1; the last was at 23:31 UTC on November 2.
- An attempt to create a new administrative cloud identity was blocked.
- Barracuda removed a read-only host-mounted container on November 4 and rotated credentials.
- No cryptocurrency wallet material was found on the searched systems.
- Customers who were not contacted were told they did not need to act.
Impact: Cloud secrets, source tokens, and Kubernetes credentials exposed
| Product | Affected |
|---|---|
| Barracuda cloud accounts | — |
- 1.Affected customers should revoke and recreate relevant integration credentials.
- 2.Replace long-lived keys with short-lived, narrowly scoped access.
- ATT&CK
- T1078.004 Valid Accounts: Cloud AccountsT1552.001 Unsecured Credentials: Credentials In FilesT1552.005 Unsecured Credentials: Cloud Instance Metadata API
- Vendors
- Barracuda
- Products
- Barracuda XDRARTEX
- Victims
- Barracuda
From the original article
3 min read at cybersecuritynews.com
Hackers used a cloud access key exposed through an AI vendor to reach approximately 10 Barracuda cloud accounts in roughly 44 hours. The intrusion moved through stored secrets, development systems, and Kubernetes clusters, showing how one forgotten credential can open a path across several connected platforms. Barracuda recorded the activity between November 1 and November […]
By Tushar Subhra Dutta · cybersecuritynews.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.