Skip to the content
AI and Cybersecurity Learning and Practice Center Test automation Open the Learning Center

IncidentAI-enabled attacks

Barracuda: an attacker that matches ARTEX used a cloud key Barracuda never retired from an AI vendor and reached about 10 cloud accounts in roughly 44 hours

HighBarracuda Networks

Barracuda's CISO Arve Kjoelen published an account on November 11, 2026 of an intrusion into parts of its cloud environment, after a Trust Center advisory on November 10. The attacker used a valid cloud access key that Barracuda had given an AI vendor for an earlier project and never retired; Barracuda says the vendor's own development environment was compromised in October and appears to be where the key was found. The first call with the key was at 04:33 UTC on November 1 and the last recorded activity at 23:31 UTC on November 2. Starting from stored secrets, the attacker moved within about a day from cloud accounts to a data analytics system, a source-code token and Kubernetes clusters, pushed short-lived branches to make a build job print its secrets in encoded form, deployed a container that mounted a host's file system, tried to create a new administrative cloud identity (blocked) and searched servers for crypto wallet material, which Barracuda says was not there. It says the attacker's probe names, work order and credential and wallet hunting all match ARTEX, the open-source AI penetration-testing framework, and cautions that many groups use it, so the match shows how the attacker worked, not who it was. About 10 cloud accounts were touched. Barracuda found no direct evidence that the credentials its XDR service uses to collect customers' data were viewed, but says its logging could not rule that out, and it does not say whether customer data was taken.

Replay the attack step by step in the Learning Center

How it happened

  1. An unretired cloud key, given to an AI vendor for an earlier project, opened the door; the vendor's own development environment had been compromised in October.
  2. Each secret the attacker read opened the next system within about a day: cloud accounts, a data analytics system, a source-code token and Kubernetes clusters.
  3. A build job triggered from short-lived branches printed its secrets in encoded form to get past log masking, and a container mounted a host's file system to harvest its credentials.

Impact

About 10 cloud accounts and several credential stores were reached in roughly 44 hours; Barracuda treated every credential within the attacker's reach as compromised.

The fix

Barracuda removed the backdoor container, rotated credentials and secrets across every affected system and contacted customers whose API integration credentials for Managed XDR Cloud or Monitored Endpoint may be affected, asking them to revoke and recreate them; customers who have not heard from it need no action.

Lessons

  • End every vendor's access when the project ends, and give each key an owner and an expiry.
  • Barracuda argues that short-lived, narrowly scoped credentials would have stopped this at the first step and that no single credential should open the next system.
  • Be ready to rotate secrets at scale and to treat everything in an attacker's reach as compromised.

Sources