
Barracuda has published its account of an intrusion into its own cloud environment. The company says the attacker did not break in: it used a valid cloud access key that Barracuda had given a third-party vendor for a past project. “We did not retire the key when the vendor — a company working in AI — finished that work. That is on us,” Barracuda writes. Its Trust Center update of November 13 says the key sat in a configuration file in the vendor’s GitHub repository, exposed when the vendor’s development environment was compromised in October.
Barracuda says the attacker made its first call with the key on November 1 at 04:33 UTC and its last recorded activity was on November 2 at 23:31 UTC, touching about 10 cloud accounts in roughly 44 hours. It read stored secrets, then chained credentials from cloud accounts to a data analytics system, a source-code access token and Kubernetes clusters. In one stage it pushed short-lived branches to a handful of repositories to trigger a build workflow that printed the build system’s secrets into the job log, encoded so the usual masking would not hide them. It also deployed a container that mounted a server’s file system to harvest credentials and tried to create a new cloud administrator identity, which was blocked. An engineer noticed odd activity on November 4, and the vendor separately contacted Barracuda that day about its own incident.
Barracuda says the probe names, order of activity and built-in credential and wallet hunting routines match ARTEX, the open-source AI-driven penetration-testing framework released in July, but stresses that many groups use it, so the match shows how the attacker worked, not who it was. The commands searched for wallet-related variables and files (WALLET, MNEMONIC, SEED, PRIV, Ethereum keystores, seed phrases); Barracuda says no wallet material existed on those systems and that the activity is consistent with a financially motivated actor, while not ruling out other motives. It compares the intrusion to the one at Railway, which we covered in our Railway incident report post; for the ARTEX tool itself, see the FBI flash alert coverage.
How to check if you’re affected
Affected products are the API integrations for Barracuda Managed XDR Cloud and Monitored Endpoint; the Trust Center advisory says organizations that use neither are not affected. One of the systems the attacker reached stores credentials that Barracuda XDR uses to collect data from customers’ connected systems such as Microsoft 365, Google Workspace and endpoint security platforms. Barracuda says it found no direct evidence those credentials were viewed or accessed, but it directly notified customers with potentially affected credentials.
If you received a notification, Barracuda’s guidance is to revoke and recreate your integration credentials and review activity within the connected systems beginning November 1, 2026. If you did not receive one, the advisory says no action is required. Barracuda’s indicators of compromise: cloud and Kubernetes resources named with the letter “i” followed by digits and no hyphen (for example i31911, i28324probe, i19engx1), and GitHub workflow files named i19ghci.yml and i19ci2.yml on branches beginning i19ghci- and i19ci2-.
