A Vendor’s Forgotten Cloud Key Opened the Door at Barracuda, and an AI Attack Tool Did the Rest. Your Questions Answered
Security company Barracuda says an attacker used a cloud access key it had given a vendor and never retired, then moved through about 10 cloud accounts in 44 hours with help from the ARTEX AI attack framework. Here are the answers to the main questions, including what Barracuda XDR customers were asked to do.
Barracuda, a well-known maker of network and email security products, has disclosed that its own cloud environment was breached at the start of November. The company’s account is unusually candid: the way in was an old access key it had handed to a vendor and forgot to switch off. BleepingComputer laid out Barracuda’s findings, and SecurityWeek placed them in the wider wave of attacks using the same AI tool. Here are the questions business owners are most likely to ask.
How did the attacker get in?
With a valid cloud access key. Barracuda had issued it to a third-party vendor, a company working in AI, for a past project. When that project ended, the key was never retired. Barracuda says it believes the attacker stole the key from the vendor in October and has confirmed the key sat in a configuration file in the vendor’s GitHub repository. In its own words: “That is on us.”
When did it happen and how long did it last?
The intrusion ran across roughly 44 hours on November 1 and 2. Barracuda found the attacker on November 4.
What did the attacker reach?
About 10 Barracuda cloud accounts. Using credentials found on one system to unlock the next, the intruder moved through a data analytics environment, source-code repositories and Kubernetes clusters, going after secret stores, configuration data, Kubernetes service accounts and server metadata services, according to SecurityWeek. On some servers the attacker had shell access and searched for cryptocurrency material such as Ethereum keystore files, seed phrases and private keys.
Did customers’ data get taken?
The attacker reached a system that stores customer integration credentials for Barracuda XDR. Barracuda says it found no evidence those credentials were accessed or stolen, but because it cannot rule it out, it asked potentially affected Managed XDR Cloud and Monitored Endpoint customers to revoke and recreate their integration credentials. Customers who were not contacted directly do not need to do anything, the company says.
Did the attacker try to stay?
Yes. A container that mounted the host’s file system, including credentials stored there, was deployed as an attempt at persistence, and SecurityWeek reports a backdoor was left in a Kubernetes cluster. A separate attempt to create a new cloud administrator identity was blocked.
What is ARTEX, and why does Barracuda think it was involved?
ARTEX is an open-source, AI-driven penetration testing framework that appeared on GitHub in July 2026. A planner sets an objective and breaks it into tasks that AI agents carry out. Its developer removed the repository in October, yet it keeps spreading, and the FBI has warned that it lets low-skill attackers run complex operations against many targets at once. Barracuda says the probe names, other indicators, the order in which the attacker worked and its built-in routines for hunting credentials and wallets all match ARTEX. It called the event a “machine-speed intrusion” and noted strong similarity to a recent breach at hosting provider Railway.
Who was behind it?
Barracuda has not named anyone, pointing out that many groups use ARTEX. Its read is that the crypto hunting points to a financial motive, though it does not rule out that this was a distraction from some other goal.
What this means for your company
Nothing in this attack required a new vulnerability. It needed one key that should have expired and a vendor that stored it in a code repository. Most small businesses have the same loose ends: API keys, app passwords and admin accounts created for a consultant, an integration or a one-off project that nobody turned off. Keep a simple register of every credential you issue to an outside party, put an end date on each one, and revoke it the day the work finishes. Ask vendors how they store your keys. Where you can, use short-lived or scoped credentials rather than permanent ones, and alert on any new administrator account. Automated attack tools work through whatever access they find in hours, so the cleanup has to happen before they arrive.
If you have never audited which vendors still hold keys to your cloud and Microsoft 365 accounts, we can help you find and retire them. Reach out to Layer 7 Data Solutions to discuss how we’ve helped companies similar to yours.
