Barracuda Links Cloud Breach to ARTEX AI Pentesting Framework

Summary
Barracuda says an attacker used a cloud key left active after a vendor project and the ARTEX AI pentesting framework to access about 10 cloud accounts over 44 hours. It found no evidence Barracuda XDR integration credentials were accessed or stolen.
Key points
- Barracuda says the attacker accessed about 10 cloud accounts between November 1 and 2; the company discovered the intrusion on November 4.
- Barracuda believes the attacker stole a cloud access key from an unnamed AI vendor in October. The key had not been retired after a project and was stored in a configuration file in the vendor's GitHub repository.
- Credentials found in one system enabled movement through Barracuda's data analytics environment, source-code repositories, and Kubernetes clusters.
- Barracuda's investigation identified machine-style labels, probing methods, and built-in hunting routines it says matched the ARTEX framework.
- The attacker attempted persistence with a container that mounted the host file system. A separate attempt to create a cloud administrator identity was blocked.
- Commands targeting cryptocurrency secrets led Barracuda to believe the activity was financially motivated, though it said the activity could have been a diversion.
- The attacker reached a system storing Barracuda XDR customer integration credentials, but Barracuda found no evidence they were accessed or stolen; potentially affected customers were asked to rotate them.
Article Details
- Victim Organization
- Barracuda
- Incident Type
- Cloud environment breach using a stolen cloud access key
- Incident Date
- 2026-11-01
- Disclosure Date
- 2026-11-16
- Operational Impact
- The attacker accessed approximately 10 Barracuda cloud accounts over 44 hours between November 1 and 2, and moved through its data analytics environment, source-code repositories, and Kubernetes clusters. The attacker reached a system storing Barracuda XDR customer integration credentials, but Barracuda found no evidence those credentials were accessed or stolen. An attempt to create a new cloud administrator identity was blocked.
- Ransom Or Extortion
- No ransom demand or extortion was reported. Barracuda said the activity appeared financially motivated based on commands targeting cryptocurrency-related secrets, but it did not rule out that this was a diversion.
- Claim Status
- confirmed
MITRE ATT&CK
T1078.004 · Cloud AccountsThe attacker used the stolen cloud access key to access Barracuda cloud accounts.T1136.003 · Cloud AccountThe attacker attempted to create a new cloud administrator identity, but Barracuda blocked the attempt.T1552.001 · Credentials In FilesThe attacker reportedly stole a cloud access key that had been stored in a configuration file in the third-party vendor's GitHub repository.T1610 · Deploy ContainerThe attacker attempted to establish persistence by deploying a container that mounted the host file system.
Vendors
Products
Barracuda XDRAccording to the cybersecurity company, the attacker reached a system that stores customer integration credentials for Barracuda XDR; however, it found no evidence that those were accessed or stolen.GitHubIt confirmed that the key was stored in a configuration file in the vendor's GitHub repository.KubernetesThe attacker used credentials they found in one system to move through Barracuda’s data analytics environment, source-code repositories, and Kubernetes clusters.
