Breach
Barracuda reports Artex-powered intrusion that exfiltrated cloud credentials and secrets
Barracuda says an Artex-powered attacker touched about 10 cloud accounts in roughly 44 hours between November 1 and 2, exfiltrating credentials and secrets.
Written by a model from the sources below. Verify against them.
- Vendor
- Barracuda
- Status
- Confirmed
- Disclosed
- Data taken
- Tokens and keys
- BleepingComputer: “The security company believes the attacker stole the key from the unnamed third-party AI vendor in October.”
- unnamed third-party AI vendor
Summary
The attacker also left a backdoor in a Kubernetes cluster and, on some servers, searched for Ethereum keystore and seed phrase files.
What to do
Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it
For tokens and keysRevoke and rotate the exposed cloud access key and any secrets reachable from it.
Audit all cloud accounts and Kubernetes service accounts for unauthorized access during November 1 to 2.
Find and remove the backdoor left in the Kubernetes cluster and review server shell access logs.
Check secret stores, configurations and metadata service access for further credential theft.
Revoke and recreate Barracuda XDR integration credentials if you are a Managed XDR Cloud or Monitored Endpoint customer.
Retire cloud access keys as soon as a third-party vendor's work ends.
Timeline
- Made public by SecurityWeek
- First seen by cve.now
- Confirmed by Barracuda
BleepingComputer: “The company says the attacker accessed approximately 10 of its cloud accounts over a 44-hour period between November 1 and 2.”
1 day - Record last updated
What was taken
| Taken | Per the source |
|---|---|
| Tokens and keys | SecurityWeek: “Barracuda , which fell victim to an Artex-powered intrusion, published similar findings: hackers used an exposed valid cloud access key to map its reach, then…” |
Evidence 4
- PressSecurityWeek
“Barracuda , which fell victim to an Artex-powered intrusion, published similar findings: hackers used an exposed valid cloud access key to map its reach, then reused discovered secrets to access more systems and exfiltrate more credentials and secrets.”
- PressBleepingComputer
“Hackers who breached the cloud environment of network and email security company Barracuda earlier this month used a stolen cloud access key and the ARTEX AI penetration testing framework.”
+1 more: BleepingComputer on Bluesky - SocialMastodon
“Barracuda: cloud breach traced to a vendor access key left live after the project ended — it sat in a config file in the vendor's GitHub repo.”
- SocialBluesky
“Barracuda Reports Cloud Security Incident Involving Exposed Vendor Key and ARTEX AI Pentesting Framework + Video”
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about the unnamed third-party AI vendor breach affecting Barracuda
Was Barracuda customer data exposed?
Yes. The breach was at unnamed third-party AI vendor, a vendor of Barracuda. Barracuda says so: “The company says the attacker accessed approximately 10 of its cloud accounts over a 44-hour period between November 1 and 2.” (BleepingComputer).
What data was exposed?
Tokens and keys.
What should Barracuda customers do?
Rotate API keys and tokens you gave it, and review the OAuth apps and integrations connected to it. Revoke and rotate the exposed cloud access key and any secrets reachable from it. Audit all cloud accounts and Kubernetes service accounts for unauthorized access during November 1 to 2. Find and remove the backdoor left in the Kubernetes cluster and review server shell access logs. Check secret stores, configurations and metadata service access for further credential theft. Revoke and recreate Barracuda XDR integration credentials if you are a Managed XDR Cloud or Monitored Endpoint customer. Retire cloud access keys as soon as a third-party vendor's work ends.