CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →
← Back to the live brief
NOTABLENATOA2incident

Barracuda's own account of a 44-hour intrusion into its cloud: a key given to an AI vendor and never retired, found in that vendor's compromised development environment, led an intruder across about ten cloud accounts to Kubernetes; notified Managed XDR customers must recreate their integration credentials

Barracuda: an unretired vendor cloud key led an ARTEX-consistent intruder across ten accounts in 44 hours

Defender actions

  • If Barracuda notified you that your Managed XDR Cloud or Monitored Endpoint integration credentials may be affected, revoke and recreate each integration credential and review activity in the connected systems (Microsoft 365, Google Workspace, endpoint security platforms and others) since 2026-11-01; Barracuda says an organisation it did not notify needs no action.

Analysis

Barracuda says the attacker did not break in but used a valid cloud access key that Barracuda had issued to a third-party vendor, a company working in AI, for an earlier project and had not retired when the work ended (Barracuda Blog, 2026-11-11). The key had been stored in a configuration file in the vendor's GitHub repository, which was exposed when the vendor's development environment was compromised (Barracuda Trust Center, 2026-11-13). The first call with the key came on 2026-11-01 at 04:33 UTC; within minutes the attacker was mapping what the key reached and reading stored secrets such as AWS access keys and Azure service principal secrets, and each secret opened the next system, from cloud accounts to a data analytics system, to a source-code access token and on to Kubernetes clusters (Barracuda Blog, 2026-11-11). In just under four hours on 2026-11-02 it pushed short-lived branches to a handful of repositories to trigger a build workflow written to print the build system's secrets into the job log, encoded so that log masking would not hide them, and its last recorded activity was at 23:31 UTC, about 10 cloud accounts and 44 hours after the start (Barracuda Blog, 2026-11-11).

In a Kubernetes cluster the attacker deployed a container that mounted the underlying server's file system read-only, enough to harvest that server's credentials, and tried to create a new administrative cloud identity, which was blocked (Barracuda Blog, 2026-11-11). On servers where it had a shell, its commands searched for environment variables named WALLET, MNEMONIC, SEED and PRIV, Ethereum keystore files, extended private keys, seed phrase files and Kubernetes secrets with wallet-related names, and Barracuda calls the activity consistent with a financially motivated actor seeking cryptocurrency and reusable credentials (Barracuda Trust Center, 2026-11-13). Barracuda says the resource names, the sequence of activity and the credential and wallet hunting routines match ARTEX, which many groups use, so the match shows how the attacker operated, not who it was (Barracuda Blog, 2026-11-11).

Cited evidence

The investigation has found no direct evidence that customer integration credentials were viewed or accessed.

The cloud access key used had been stored in a configuration file within the third party’s GitHub repository, which was exposed when the third party’s development environment was compromised.

Barracuda Trust Center

Because many groups use ARTEX, the match tells us how the attacker operated, not who it was.

Barracuda Blog 2026-11-11

Sources2

PROVENANCE

AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.