Incidents

Barracuda Breach: Attacker Used ARTEX and a Stolen Cloud Access Key

Barracuda says an attacker used ARTEX and a stolen access key left active after a vendor project to breach about ten of its cloud accounts.

Barracuda Breach: Attacker Used ARTEX and a Stolen Cloud Access Key

Barracuda has disclosed that an attacker used a stolen cloud access key and the ARTEX tool to break into its cloud environment. According to the company, the intruder had access to roughly ten accounts for about 44 hours on November 1 and 2. The activity was detected on November 4. Barracuda has not attributed the attack to any specific threat group.

How the incident unfolded

The access key had been issued to a third-party vendor for a project, but it was never revoked after the engagement ended. Barracuda believes the attacker stole the key from the vendor in October. The key was sitting in a configuration file in the vendor’s GitHub repository.

The attacker used credentials found on one system to move laterally across Barracuda’s data analytics environment, source code repositories, and Kubernetes clusters. The company says commands targeting cryptocurrency-related secrets point to a possible financial motive, although Barracuda has not ruled out that this activity was meant to distract from the attacker’s real objective.

Lessons for organizations

The incident shows how access keys left in place after a project wraps up can become a path into production environments. Organizations should keep an inventory of keys and tokens, assign each one an owner and an expiration date, and revoke access whenever the scope of a vendor relationship changes. It’s also worth monitoring credential use in event logs, especially for accounts that connect production systems to external services.

If your organization uses Barracuda integrations, check the company’s official notifications and follow the instructions you receive. Coordinate any credential changes with service administrators so that existing connections aren’t disrupted.

SecurHUB’s take

Vendor technical access should be limited to what’s strictly necessary, and every credential needs an owner and a managed lifecycle. Security audits can help verify that these policies also cover your cloud integrations.

Sources: BleepingComputer, SecurityWeek

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk