Barracuda said in a November 11 blog post that an attacker got into its cloud systems using one valid access key. Barracuda had given the key to an AI vendor for earlier work and never switched it off. It says the vendor's own development setup was hacked in October, which appears to be where the key was found. The attacker reached about 10 cloud accounts in roughly 44 hours, from November 1 to 2. Barracuda says the pattern matches Artex, an AI-driven testing tool.
Barracuda says the key let the attacker read stored secrets, and each secret led to the next system: an analytics system, a source-code token, then Kubernetes clusters. It also says the attacker pushed short-lived branches that ran a build job printing the build system's secrets into its log. The secrets were encoded, so masking did not hide them. Barracuda found no direct sign the attacker saw the credentials its XDR service uses for customer data, but its logs could not rule it out. It contacted customers who could be affected.
Barracuda's own lesson is that no single credential should open the next door. Here, each credential the attacker found did. A vendor's key is only as safe as the last system that holds it, so ask who holds yours and who retires it when a project ends.