Skip to main content
Back
IntrusionSaaS · Kubernetes
3 min read

A former vendor’s cloud key gave an attacker access to Barracuda

Victim
Barracuda Networks
When
Nov 1–2, 2026Disclosed Nov 10, 2026
Entry
An attacker used a cloud access key that Barracuda had left active after a vendor finished its project.

Barracuda left a cloud key active after a vendor finished its project. On November 1 and 2, an attacker used the key to enter Barracuda’s environment and reached about ten cloud accounts in roughly 44 hours. One affected system held credentials for monitoring customers’ systems, and Barracuda could not establish whether anyone read them.

What happened

Third party
Former vendor
Internet
Vendor access key
Stored credentials
Analytics system
Barracuda cloud accounts
GitHub repositories
Kubernetes cluster
Build jobs
Workload container
Worker server

Barracuda’s November 2026 cloud intrusion / A key from a completed vendor project was still active.

  1. 1

    Vendor access persisted

    November 1, 2026

    The cloud key still worked after the vendor’s project ended. Barracuda reported that it opened access to stored credentials.

  2. 2

    Build secrets targeted

    November 2, 2026

    The attacker pushed new GitHub branches to try to expose build secrets in job logs. Barracuda did not say whether the jobs ran or any secrets appeared in the logs.

  3. 3

    Server credentials taken

    November 1–2, 2026

    In a Kubernetes cluster, a container with read-only access to the underlying server’s files exposed that server’s credentials. The time relative to the GitHub activity is unknown.

Impact

The attacker reached about ten Barracuda cloud accounts, read stored cloud credentials and took credentials from a server. It also reached a system holding customer integration credentials. Gaps in Barracuda’s logs left it unable to determine whether anyone read the customer credentials.

Could this have been prevented?

Close vendor access when the work ends

Revoking the vendor’s key when its project ended would have closed the documented entry point. Inside your environment, GitHub can restrict who creates branches that trigger builds. Kubernetes can reject containers requesting a hostPath volume. Barracuda did not identify the GitHub account’s privileges or the volume type in this cluster.

Incident control assessments

0
Prevented
2
Contained
1
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Third party
Former vendor
Internet
Vendor access key
Stored credentials
Analytics system
Barracuda cloud accounts
GitHub repositories
Kubernetes cluster
Build jobs
Workload container
Worker server

Barracuda’s November 2026 cloud intrusion / A key from a completed vendor project was still active.

1 · Vendor access persisted

1 Not covered

2 · Build secrets targeted

1 Contained

3 · Server credentials taken

1 Contained

Key facts

  • On November 1 at 04:33 UTC, the attacker first used the key. Barracuda later confirmed that a configuration file in the vendor’s GitHub repository had held it.
  • On November 2, the attacker pushed new branches to several GitHub repositories to try to expose build secrets. Separately, Barracuda confirmed that the attacker obtained credentials from a server in its Kubernetes cluster.
  • Barracuda recorded the last activity on November 2 at 23:31 UTC. An attempt to create a new cloud administrator identity had failed. Barracuda did not identify what blocked it.
  • On November 4, a Barracuda engineer reported unusual activity and the vendor notified the company of its own breach. Barracuda removed the container that evening, Pacific time, and rotated credentials.
  • On November 10, Barracuda said it had notified customers with potentially affected integrations. It advised them to replace those credentials and review connected-system activity dating back to November 1.

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Forty-four hours: Anatomy of a machine-speed intrusionBarracuda Networks · Nov 11, 2026 · Vendor reportThe company’s timeline, cloud accounts reached, attempt to expose build secrets, host credentials taken and response.
  2. 2.
    Barracuda XDR Integration CredentialsBarracuda Networks · Nov 13, 2026 · AdvisoryThe November 10 advisory and its November 13 update confirm the key’s location, systems reached and limits of the evidence about customer credentials.
  3. 3.
    Barracuda XDR Integration Credentials — customer guidanceBarracuda Networks · Nov 11, 2026 · Vendor reportInstructions for notified customers to replace integration credentials and verify that data collection works afterward.
  4. 4.
    Available rules for rulesetsGitHub · undated · Vendor reportThe Restrict creations rule and its exception for identities with bypass permission.
  5. 5.
    Pod Security AdmissionKubernetes · undated · Vendor reportNamespace enforcement, Pod admission and exemptions.
  6. 6.
    Pod Security StandardsKubernetes · undated · Vendor reportThe Baseline standard forbids hostPath volumes, including read-only mounts.

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns