Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 3 min · 550 words
- Severity
- Routine
Barracuda Cloud Breach Traced to St Vendor Key and AI Pentesting Tool
Barracuda says an attacker used a stolen vendor cloud key and the ARTEX AI pentesting framework to reach 10 cloud accounts in 44 hours on November 1-2.

Event log
- Attacker accessed ~10 Barracuda cloud accounts over 44 hours on November 1-2; detected November 4.
- Intrusion used a cloud access key left unretired after a third-party AI vendor project, stored in a GitHub config file.
- Barracuda attributes the attack to the open-source AI pentesting framework ARTEX.
- Attacker reached the system storing Barracuda XDR customer integration credentials; no evidence of theft.
- Managed XDR Cloud and Monitored Endpoint customers asked to revoke and recreate integration credentials.
A stolen cloud access key and an open-source AI penetration testing framework gave an attacker a 44-hour run through Barracuda's cloud environment on November 1 and 2. The intruder reached roughly 10 of the security company's cloud accounts before Barracuda detected the presence on November 4.
The investigation identified the tool as ARTEX, an open-source AI pentesting framework, and Barracuda characterized the incident as a machine-speed intrusion. What does this change for CIOs running third-party integrations? Quite a lot, because the failure was not exotic — it was an unretired credential.
Where did the key come from?
The attacker leveraged a cloud access key that Barracuda had provided to a third-party vendor for a previous project. The vendor, a company working in AI, kept the key stored in a configuration file inside its GitHub repository.
"We did not retire the key when the vendor — a company working in AI — finished that work. That is on us," Barracuda said. The company believes the attacker stole the key from the unnamed vendor in October.
How far did the intrusion reach?
Once inside, the attacker chained credentials found in one system to move through three distinct zones of Barracuda's estate:
- The data analytics environment
- Source-code repositories
- Kubernetes clusters
Commands recovered during the investigation targeted cryptocurrency-related secrets, including private keys, Ethereum keystore files and seed phrases. Barracuda assesses the attack as financially motivated, though it does not rule out that the crypto hunting served as a diversion from a true motive.
Persistence attempts followed. The threat actor deployed a container that mounted the host's file system, including credentials stored on it. A separate attempt to create a new cloud administrator identity was blocked.
Barracuda attributed the activity to ARTEX based on machine-style labels, certain probing methods and built-in hunting routines matching the framework. The company also noted the attack closely resembled a recent incident at cloud hosting provider Railway, which likewise involved credential chaining and the apparent use of ARTEX.
What does this mean for customers?
The attacker reached a system that stores customer integration credentials for Barracuda XDR. Barracuda found no evidence those credentials were accessed or stolen, but given the uncertainty, it asked potentially affected Managed XDR Cloud and Monitored Endpoint customers to revoke and recreate their integration credentials.
Customers who did not receive direct communication about the incident need take no action, the company said.
The operational lessons are blunt. A key issued to a contractor outlived its project and sat in a plaintext configuration file in a GitHub repository — two lapses that turned a finished engagement into an open door. Offboarding a vendor apparently did not include offboarding the vendor's credentials. The ARTEX angle adds speed to an old story: once the key leaked in October, the machine-speed reconnaissance, lateral movement and persistence attempts all arrived in a two-day window that ended only when detection caught up on November 4.
For security teams, the checklist writes itself. Retire third-party access keys when projects close, scan repositories for embedded credentials, and assume that an AI-driven framework will enumerate a cloud estate faster than a human operator ever did. Barracuda admitted the first point itself. The rest of the industry should take the hint.
via bleepingcomputer.com (Source)
More from Tom Whitfield
Show full bio
Market editor covering people, launches and day-to-day practice in enterprise information technology and the leaders who run at CIO Monitor.
185 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- Operation ShadowCloud: Backdoors Hide C2 in GitHub, SharePoint and Ably
- 4,837 GitHub accounts hijacked to steal cloud and CI credentials
- Cursor Breach Exposed 5,000 Developers to Malicious Claude Code
- Railway Breach Cost Hits $740,000 as Stolen AI Keys Resold
- Railway Breach Cost $740,000 in Fraudulent AI Usage