---
id: "CMP-202611-enzt3v"
page: "https://infrastack.ai/live/CMP-202611-enzt3v"
kind: "campaign"
aliases: []
title: "Barracuda breached through a forgotten vendor cloud key: attacker reached the system holding Barracuda XDR customers' integration credentials (Microsoft 365, Google Workspace, EDR); notified customers must recreate them"
severity: "high"
cvss: null
epss: null
exploited: true
status: "open"
category: "vendor"
products: [{"name": "Barracuda Managed XDR", "note": "API integrations for Managed XDR Cloud or Monitored Endpoint; credentials possibly exposed Nov 1-2, 2026", "fixed": [], "ecosystem": "saas"}, {"name": "Barracuda", "note": "disclosed by the company", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["ai-hacking", "breach", "campaign", "early-warning", "vendor", "xdr"]
not_affected_if: []
published_at: null
first_seen_at: "2026-11-16T09:55:52+00:00"
updated_at: "2026-11-16T10:06:41+00:00"
sources: [{"source": "analyst", "url": "https://trust.barracuda.com/security/barracuda-xdr-integration-credentials", "first_seen_at": "2026-11-16T09:55:52+00:00", "cites": ["https://trust.barracuda.com/security/barracuda-xdr-integration-credentials", "https://it.blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"]}]
exploit_sources: []
---

# Barracuda breached through a forgotten vendor cloud key: attacker reached the system holding Barracuda XDR customers' integration credentials (Microsoft 365, Google Workspace, EDR); notified customers must recreate them

Link for people: https://infrastack.ai/live/CMP-202611-enzt3v (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- saas:Barracuda Managed XDR affected range not listed fixed no fixed version listed
- vendor:Barracuda affected range not listed fixed no fixed version listed

## Cause

How the attacker got in: a secret readable from the internet (exposed-secret). The attacker used a cloud access key Barracuda had given an AI vendor and never revoked, which was found in a config file in the vendor's GitHub repo, and customers' stored integration credentials then went with the breach.

How it reached others: customers' data or keys went with it (third-party-breach).

So it does not happen to you: Check that no deployed app serves .env files or env bundles, and scan your repos and their history for keys; rotate what you find, do not just delete the line.

Last month's incidents with the same cause, and the full checklist: https://infrastack.ai/live/breaches.md#third-party-breach

## How to check

Do you use Barracuda Managed XDR Cloud or Monitored Endpoint with an API integration, and did you get a notification from Barracuda? In connected systems (Microsoft 365, Google Workspace, EDR and other integrated services), review activity by the Barracuda XDR integration app or service account from 1 November 2026 onward. Barracuda'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-. Further IOCs are in Barracuda's 'Forty-four hours' write-up.

## Fix

If notified: revoke and recreate the integration credentials you gave Barracuda XDR (API keys, app secrets, service principals) and review activity in the connected systems since 1 November 2026. If you were not notified, Barracuda says no action is needed. In general, expire any cloud keys you have handed to vendors once their work ends.

## Timeline

- 2026-11-10T00:00:00+00:00 confirmed by Barracuda (blog) https://trust.barracuda.com/security/barracuda-xdr-integration-credentials
- 2026-11-11T00:00:00+00:00 confirmed by Barracuda (blog) https://it.blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion "Earlier this month, Barracuda was the target of a fast-moving intrusion into parts of our cloud environment."
- 2026-11-16T09:55:52+00:00 analyst https://trust.barracuda.com/security/barracuda-xdr-integration-credentials

## Documents

- [describes] @campuscodi.risky.biz: N: news.risky.biz/risky-bullet...
P: risky.biz/RBNEWS634/

-Hackers accessed Bar https://bsky.app/profile/campuscodi.risky.biz/post/3n2ga5t5msc2w
- [describes] Barracuda XDR Integration Credentials https://trust.barracuda.com/security/barracuda-xdr-integration-credentials
- [describes] Forty-four hours: Anatomy of a machine-speed intrusion (Barracuda) https://it.blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
