Incident
Published 2026-11-10 New
Verified 2026-11-17

Barracuda says an attacker used a cloud access key issued to a third-party vendor to move through parts of its cloud environment on 1-2 November 2026; notified Managed XDR Cloud and Monitored Endpoint customers asked to revoke and recreate integration credentials

Barracuda said in a Trust Center advisory published on 10 November 2026 that in early November it identified unauthorized activity within portions of its internal cloud environment, that the attacker gained access through a third party that had been issued a cloud access key, and that the attacker sought credentials stored across the environment and used them to move laterally.

Barracuda says one affected system stores the credentials Barracuda XDR uses to collect data from customers' connected systems, such as Microsoft 365, Google Workspace and endpoint security platforms; the attacker had access to it on 1-2 November 2026, and the investigation found no direct evidence that customer integration credentials were viewed or accessed. Barracuda has directly notified customers with potentially affected credentials and asked them to revoke and recreate integration credentials and review connected-system activity since 1 November 2026; the advisory applies only to organizations using an API integration for Barracuda Managed XDR Cloud or Monitored Endpoint, and organizations that were not notified need take no action.

Barracuda says commands the attacker ran searched for cryptocurrency wallets and related assets, and that the activity is consistent with a financially motivated threat actor.

The advisory lists IP addresses and user agents as indicators of compromise. (source: Barracuda Trust Center) In a technical write-up dated 11 November, Barracuda says it did not retire the key when the vendor, a company working in AI, finished a previous project ("That is on us"); that the vendor's own development environment was compromised in October; and that the attacker moved from its cloud accounts to a data analytics system, a source-code access token and Kubernetes clusters, touching about 10 cloud accounts in roughly 44 hours, deployed a container that mounted a server's file system to harvest its credentials, and was blocked when it tried to create a new administrative cloud identity.

Barracuda says the attacker's labels, probes and credential- and wallet-hunting routines match ARTEX, an open-source AI-driven penetration-testing framework, and that because many groups use ARTEX the match shows how the attacker operated, not who it was. (source: Barracuda blog)

UPDATE (13 Nov 2026, 2:30 pm EST; 14 Nov 03:30 Perth): Barracuda says the key had been stored in a configuration file in the third party's GitHub repository, exposed when the third party's development environment was compromised; other Barracuda credentials in the same file had already expired or have since been revoked; it retired two internal automation servers whose credentials were exposed and found no evidence of attacker activity on them; and the investigation remains ongoing. (source: Barracuda Trust Center)

BleepingComputer reported the incident on 16 November 2026. (source: BleepingComputer)

Product
Barracuda internal cloud environment; Barracuda Managed XDR Cloud and Monitored Endpoint API integration credentials
Patch to
Customers notified by Barracuda: revoke and recreate Barracuda XDR integration credentials and review connected-system activity logs since 1 November 2026 (guidance on Barracuda Campus; questions to SOC@Barracuda.com). Barracuda says organisations it has not notified need take no action. Check environments for the IP addresses and user agents in Barracuda's advisory.

breaches cloud