Technical · Global
Barracuda Says Unrevoked Vendor Key Let AI Attackers Into Ten Cloud Accounts
The email security vendor said a stolen access key and the ARTEX automated attack framework fueled a 44-hour intrusion that reached systems behind its XDR platform.
By vaayaa News Desk · · 3 min read

Barracuda Networks disclosed on November 16 that an intruder reached about 10 of its cloud accounts during a roughly 44-hour window between November 1 and 2, after obtaining a cloud access key the company had issued to a third-party vendor and failed to revoke. The security vendor said its investigation, described in a post-mortem, linked the intrusion to the open-source ARTEX automated penetration testing framework, which it characterized as an attack carried out at machine speed.
The company said it learned of the activity on November 4, two days after the attacker's last known actions, after the AI vendor alerted it and one of its engineers noticed unusual behavior on a personal account. Barracuda believes the key was stolen from the unnamed AI vendor in October and was stored in a configuration file in that vendor's repository on GitHub.
How the intruder moved
According to the company, credentials found in one system allowed the attacker to move through Barracuda's data analytics environment, its source-code repositories and its Kubernetes clusters. The intruder tried to establish persistence by deploying a container that mounted the host file system, including credentials stored there, and a separate attempt to create a new cloud administrator identity was blocked.
Barracuda said the attacker ran queries aimed at cryptocurrency-related secrets, including private keys, Ethereum keystore files and seed phrases, and assessed the activity as financially motivated. The company added that it could not rule out that the crypto-focused activity was a diversion from another objective.
Part of the unauthorized access touched environments that support Barracuda's extended detection and response platform. The company said the attacker reached a system that stores customer integration credentials for that service but found no evidence the credentials were accessed or taken. Because of the remaining uncertainty, it asked potentially affected managed detection and endpoint customers to revoke and recreate their integration credentials.
A framework authorities are tracking
Barracuda said the attack matched patterns seen in a recent incident at cloud hosting provider Railway, which also involved chained credentials and the apparent use of ARTEX. The company declined to attribute the intrusion to a specific group because multiple actors have adopted the tool. Reporting compiled in the same news cycle noted that the FBI issued an alert warning that ARTEX has been used against organizations across many sectors since August, and that a threat intelligence team at Amazon observed AI agents built on the framework probing exposed AI applications to steal provider keys.
The case places cybersecurity incident response in the spotlight for organizations that rely on outside suppliers. Barracuda attributed the root cause to its own housekeeping, stating that the key should have been retired when the vendor finished its work. The failure was not a novel software flaw but an access credential that outlived the project it was created for, a category of risk that security teams often struggle to track across cloud estates.
For workers in security operations, cloud engineering and software supply chains, the episode points to the skills employers are prioritizing: maintaining inventories of third-party access, automating key rotation, monitoring Kubernetes and source-code repositories for unexpected activity, and recognizing automated attack traffic that does not follow human pacing. Analysts note that frameworks like ARTEX lower the barrier for less skilled actors by bundling standard intrusion techniques against weak credentials, exposed services and unpatched software.
What to watch next is whether regulators and customers press for more detail on the third-party vendor's role and on the credentials issued to external partners across the industry. Barracuda has published its account of the timeline, and the FBI alert suggests ARTEX activity is broader than any single victim. Companies that have handed cloud keys to contractors or AI service providers face a straightforward question: whether those keys are still live and who is responsible for retiring them.
Written by the vaayaa News Desk, based on public reports, company statements and official data.