CiberLATAMbywhalemate

Barracuda linked cloud breach to ARTEX

Barracuda tied a 44-hour intrusion to an exposed GitHub key. The case reached nearly 10 cloud accounts.

Whalemate Labs · AI-assisted researchPublished:2 min read

Barracuda would have detected activity lasting about 44 hours that reached nearly 10 cloud accounts after an access key was stored in a configuration file inside a third-party provider’s GitHub repository, according to available coverage.

Barracuda would have detected an intrusion that lasted about 44 hours and reached nearly 10 cloud accounts, according to available coverage. Reporting attributed to the company by several outlets links the initial access to a cloud access key stored in a configuration file inside a third-party provider’s GitHub repository.

How would the attacker have gotten in?

Available coverage indicates that the starting point would have been a cloud access key exposed in a GitHub configuration file belonging to a third-party provider. From that access, technical sources describe lateral movement through a data analytics environment, source code repositories, and Kubernetes clusters. Barracuda, according to those same references, would have notified potentially affected customers directly.

What did Barracuda say about the scope?

Barracuda would have warned that a system storing XDR integration credentials was accessible during the incident, although there would be no direct evidence that those credentials were read or used. Otecosystem said the records would not rule that out entirely. The company also recommended revoking and recreating integration credentials, especially for Managed XDR Cloud or Monitored Endpoint customers.

What tools and searches were observed?

Barracuda’s investigation would have identified the open source penetration testing framework ARTEX and described the intrusion as an automated, fast-moving operation. BleepingComputer notes that the use of ARTEX does not amount to attributing the attack to a specific actor. GBHackers, meanwhile, said that during movement through the infrastructure the attacker searched for reusable secrets and cryptocurrency wallets, although it did not present evidence of successful exfiltration or impact on customers.

What was confirmed and what was not?

Available sources agree that the incident affected cloud accounts and that the exposure would have originated from a third party’s credentials. They also agree that there is no public evidence in the material reviewed of a confirmed impact on Latin American customers. What the sources do not confirm is whether the integration credentials were actually read or used, or whether there was data theft or any subsequent customer impact.

Sources

View all