NEWS

Barracuda Traces Cloud Breach to a Stolen Vendor Key and the ARTEX AI Framework

A forgotten cloud key from an AI vendor's GitHub repo let an attacker using ARTEX reach about 10 Barracuda cloud accounts in 44 hours. XDR customers must rotate credentials.

Dylan H.

News Desk

November 17, 2026
2 min read
Barracuda Traces Cloud Breach to a Stolen Vendor Key and the ARTEX AI Framework

Overview

Barracuda says the attacker who breached its cloud environment earlier this month used a stolen cloud access key together with ARTEX, an open-source AI penetration testing framework. The company called it a "machine-speed intrusion." The tool has featured in recent warnings, including an FBI flash alert and Amazon's report on AI agents hunting LLM keys.

Timeline

  • October: The key was reportedly stolen from a third-party AI vendor. Barracuda had given it to the vendor for an earlier project and never retired it. The vendor stored it in a configuration file in its GitHub repository. Barracuda said, "That is on us."
  • November 1-2: The attacker accessed about 10 cloud accounts over 44 hours.
  • November 4: Barracuda discovered the intrusion.

What the Attacker Did

The attacker moved through the data analytics environment, source-code repositories and Kubernetes clusters. Commands went after crypto-related secrets such as private keys, Ethereum keystore files and seed phrases. Barracuda believes the motive was financial but does not rule out a diversion.

For persistence, the attacker deployed a container that mounted the host file system, including stored credentials. An attempt to create a new cloud administrator identity was blocked. Barracuda matched machine-style labels, probing methods and built-in hunting routines to ARTEX, and noted similarity to a recent breach at cloud host Railway.

Customer Impact

The attacker reached a system holding customer integration credentials for Barracuda XDR. Barracuda found no evidence they were accessed or stolen, but as a precaution asked potentially affected Managed XDR Cloud and Monitored Endpoint customers to revoke and recreate their integration credentials. Customers who received no direct message need take no action.

Takeaways

  • Expire vendor-issued cloud keys when a project ends and prefer short-lived, scoped credentials.
  • Scan repositories, including vendors', for committed secrets.
  • Alert on new containers mounting host paths and on attempts to create admin identities.

Sources