Barracuda says an attacker used an old vendor access key to enter its internal cloud environment on November 1–2, 2026. One reachable system stored credentials for customer-connected services. Notified customers should revoke and recreate those integration credentials and review connected-system activity from November 1 onward.

The advisory was published November 10 and updated November 13. Bill Toulas’s November 16 report brings renewed attention to that investigation. This is separate from Barracuda’s appliance vulnerabilities; patching an email gateway does not replace the cloud credential response.

A completed project left working access behind

In his November 11 technical account, Barracuda security chief Arve Kjoelen says the company failed to retire a key after a third-party project ended. The November 13 advisory confirms it was stored in a configuration file in the vendor’s GitHub repository. The vendor’s compromised development environment exposed it.

Barracuda describes a chain through cloud accounts, a data analytics system, source-code access and Kubernetes clusters. It says the attacker touched about ten cloud accounts over roughly 44 hours. Short-lived repository branches triggered build workflows that exposed build secrets. A container also obtained host credentials through a read-only mount of the underlying filesystem.

The company discovered the incident on November 4, after the recorded activity had ended. It removed the container and rotated credentials across affected systems. An attempt to create a new administrative cloud identity was blocked.

Evidence status: vendor-reported production intrusion. Barracuda associates the activity with ARTEX, an AI-assisted security-testing framework, based on resource names and observed routines. That tooling match identifies neither the operator nor how much human direction was involved.

Which customers should act

The advisory concerns API integrations for Barracuda Managed XDR Cloud or Monitored Endpoint. XDR is a security service that combines signals from connected systems. Those integrations can hold access to Microsoft 365, Google Workspace, endpoint platforms and other services.

Barracuda found no direct evidence that customer integration credentials were accessed, but says logging was insufficient to rule it out. It therefore treated reachable credentials as potentially compromised and contacted affected customers.

  • If notified: replace the identified integration credentials using Barracuda’s customer guidance. Verify that the replacement works and the old credential has been revoked.
  • Review connected services: inspect activity from November 1, following the vendor’s investigation guidance. Credential replacement cannot explain what happened before revocation.
  • If not notified: Barracuda says no action is required under this advisory. Organizations without either listed integration are outside its stated scope.

For other operators, the incident supports removing vendor access when work ends, limiting each credential’s reach and recording access to secret stores. A read-only filesystem mount can still expose credentials that authorize writes elsewhere.

Caveat: Barracuda is both the affected company and a security vendor. Its investigation remains ongoing, and the reviewed reporting relies on its account rather than independently establishing customer credential theft.