Skip to content
NewA calmer, faster ZeroHour

Stolen AI vendor key reached about 10 Barracuda cloud accounts

Original title: Hackers Exploit Exposed AI Vendor Key to Breach 10 Barracuda Cloud Accounts in 44 Hours

Cyber Security Newsby Abinaya ()2 min read1
Part of a story covered by 8 sourcesBarracuda links 44-hour cloud breach to leftover key and ARTEXMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Over November 1–2 the attacker moved from cloud secrets into analytics, source code, and Kubernetes; creating an admin identity was blocked.

Attackers used a cloud access key left in an unnamed AI vendor’s GitHub configuration file after that vendor’s development environment was compromised in October. Barracuda said the key remained active after the project ended and, starting at 04:33 UTC on November 1, was used to read secrets and reach analytics, source code, and Kubernetes. Barracuda associated resource names and workflow patterns with ARTEX but did not identify the attacker. It removed a container, rotated credentials, and told notified customers to recreate Barracuda XDR integration credentials.

Unconfirmed: The ARTEX link is based on tool patterns and does not identify the attacker; XDR credential access is unconfirmed.

Key facts
  • The key was stored in a configuration file in the vendor’s GitHub repository.
  • Temporary branches triggered builds that printed encoded secrets into job logs.
  • Searches sought wallet and private-key material; Barracuda said none was present.
  • Incomplete logging left access to XDR integration credentials unruled-out.
Security assessment · AI, from the article

Impact: Access to cloud secrets, analytics, source code, and Kubernetes

What to do
  1. 1.Notified customers should recreate XDR integration credentials and review activity from November 1.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at cybersecuritynews.com

Hackers used a cloud access key exposed through an unnamed AI vendor to enter Barracuda’s cloud environment and reach about 10 accounts in roughly 44 hours. The November 1–2 intrusion crossed cloud services, data analytics, source code, and Kubernetes systems as the attacker collected credentials to keep moving. Barracuda said the key remained active after […]

Cyber Security News

By Abinaya · cybersecuritynews.com

Read the full article at Cyber Security News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.