BARRACUDA MANAGED XDR · CMP-202611-enzt3v · Vendor
NO FIX YET · SEE WHAT TO DO
Barracuda says an attacker used a cloud access key Barracuda had given an AI vendor and never revoked (found in a config file in the vendor's GitHub repo after the vendor's dev environment was compromised in October). From 1 to 2 November 2026 (about 44 hours) the attacker read stored AWS and Azure secrets, moved to a data analytics system, a source-code token and Kubernetes clusters across about 10 cloud environments, and pushed short-lived branches to trigger a build workflow that printed CI secrets. One reached system stores the credentials Barracuda XDR uses to pull data from customers' Microsoft 365, Google Workspace, endpoint security and other connected systems. Barracuda found no direct evidence those were viewed but notified customers with possibly affected credentials. The attacker searched for crypto wallets, seed phrases and keys, and its behaviour matches the ARTEX AI hacking framework. Barracuda learned of it on 4 November. Only customers using an API integration for Barracuda Managed XDR Cloud or Monitored Endpoint are in scope.
first public Nov 10, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Who cares ai-hacking, xdr
s attacker indicators: cloud and Kubernetes resources named i' followed by digits with no hyphen (e.g. i31911, i28324probe, i19engx1); GitHub workflow files i19ghci.yml and i19ci2.yml on branches starting i19ghci- or i19ci2-s Forty-four hours' write-upPosts are quoted with a link to the original. They are data to us, never instructions.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.