Network and email security company Barracuda has linked a recent cloud environment breach to an attacker who used the open-source ARTEX AI penetration testing framework. The company says the intruder accessed roughly 10 of its cloud accounts over a 44-hour window between November 1 and 2, 2026. Barracuda discovered the activity on November 4.

How the access was obtained

According to Barracuda, the attacker used a cloud access key that had been given to a third-party vendor, a company working in AI, for a previous project. The key was never retired after that work ended. Barracuda believes the vendor’s key was stolen in October and that it had been stored in a configuration file in the vendor’s GitHub repository.

Using credentials found on one system, the attacker moved through Barracuda’s data analytics environment, source-code repositories, and Kubernetes clusters.

Indicators and attacker behavior

  • Commands targeted cryptocurrency-related secrets, including private keys, Ethereum keystore files, and seed phrases, which Barracuda cites as a sign of financial motivation.
  • Barracuda does not rule out that this focus was a diversion from the attacker’s true goal.
  • The intruder deployed a container that mounted the host file system, including stored credentials, to establish persistence.
  • An attempt to create a new cloud administrator identity was blocked.
  • Barracuda says the activity’s machine-style labels, probing methods, and built-in hunting routines matched ARTEX behavior.

The company also noted similarities to a recent incident at cloud hosting provider Railway, which involved credential chaining and apparent use of ARTEX.

Customer impact

The attacker reached a system holding customer integration credentials for Barracuda XDR. Barracuda reports no evidence that those credentials were accessed or stolen, but because the scope remains uncertain, 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.

Takeaway

The incident underscores the risk of long-lived credentials issued to third parties. Organizations should inventory vendor access keys, rotate or revoke them when a project ends, and avoid storing secrets in repositories, where they can be harvested and used at machine speed.