AEGLIX News
Barracuda revealed that its cloud environment was compromised earlier in November when attackers leveraged a stolen cloud access key alongside the ARTEX AI penetration testing framework. The intrusion unfolded across roughly 10 Barracuda cloud accounts during a 44-hour window spanning November 1 through 2, though the company only detected the adversary's presence on November 4. Investigators determined the key was likely taken from an unidentified third-party AI vendor in October and verified it had been stored in a configuration file inside that vendor's GitHub repository. Using credentials discovered in a single system, the attacker pivoted through Barracuda's data analytics platform, source-code repositories, and Kubernetes clusters.
The adversary tried to gain a lasting foothold by launching a container that mounted the host's file system, thereby exposing credentials stored there, while a parallel effort to mint a new cloud administrator identity was thwarted. Commands that hunted for cryptocurrency-related secrets -- such as private keys, Ethereum keystore files, and seed phrases -- led Barracuda to assess the operation as financially motivated, though the firm does not exclude the possibility that this focus serves as a diversion. The company noted the intrusion bore machine-style labels, probing techniques, and built-in hunting routines consistent with ARTEX, and drew parallels to a recent breach at cloud hosting provider Railway that also featured credential chaining and apparent ARTEX activity.
The attacker managed to reach a system housing customer integration credentials for Barracuda XDR; nevertheless, Barracuda's investigation uncovered no indication that those credentials were actually viewed or exfiltrated. This conclusion stems directly from the cybersecurity firm's own examination of the breach's scope.
Given the lingering uncertainty, Barracuda has urged potentially impacted Managed XDR Cloud and Monitored Endpoint customers to revoke and regenerate their integration credentials, while customers who have not received direct notification need not take any action. The company has not signaled any additional remediation measures beyond this credential rotation guidance for the identified customer groups.
Report prepared 2026-11-16 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)