Threat feed

Barracuda ARTEX cloud intrusion

Unretired AI-vendor cloud key let an ARTEX-driven attacker chain through Barracuda's cloud for 44 hours

Posted · Spectrum Delta Research Team

Summary

An unattributed attacker used a cloud access key that Barracuda issued to a third-party AI vendor and never retired, stolen when that vendor was compromised in October, to run a 44-hour machine-speed intrusion across about 10 Barracuda cloud accounts on November 1 and 2, chaining secrets into analytics, source-code and Kubernetes systems (A/1). Probe names, work order and wallet-hunting routines match the open-source ARTEX AI penetration-testing framework, showing how the attacker worked, not who it was. The attacker read AWS and Azure secrets, decrypted infrastructure-as-code state files, took credentials from metadata services and Kubernetes service accounts, and pushed branches that made a build workflow print encoded secrets into its job log. It deployed a read-only Kubernetes container mounting a server file system to harvest credentials, tried and failed to create a new administrative cloud identity, and searched servers with shell access for wallet and seed material. Barracuda reached a system storing XDR customer integration credentials with no evidence they were viewed; affected customers must revoke and recreate them.

Breakdown

Targets

Organizations

  • Organization: Barracuda Networks

Technical exposure

  • Cloud keys issued to third-party vendors and not retired after projects end
  • Vendor secrets stored in configuration files in GitHub repositories
  • AWS access keys and Azure service principal secrets in cloud secret stores
  • Infrastructure-as-code state files containing decryptable credentials
  • Build workflows that can print job-log content that evades secrets masking
  • Kubernetes nodes allowing containers that mount the host file system

Adversary

Unattributed (ARTEX-consistent tradecraft; Barracuda assesses financially motivated) · Barracuda (A/1)

Procedures (5)

  1. Dormant vendor cloud key used for initial access

    Logs

    • CloudTrail · First use of a dormant long-lived access key issued to a third party, followed within minutes by resource-mapping and secret-reading calls (GetSecretValue, ListSecrets) from an unknown source; first call November 1 04:33 UTC
    • Azure Activity Log · API use by service principals whose secrets were stored in secret stores reachable from the compromised vendor key
  2. Credentials chained from secret stores to Kubernetes

    • T1552.005Unsecured Credentials: Cloud Instance Metadata API
    • T1528Steal Application Access Token
    • T1136.003Create Account: Cloud Account

    Logs

    • CloudTrail · AssumeRole and key-usage chains where each discovered secret is used from a new cloud account: cloud accounts, then a data analytics system, then a source-code access token, then Kubernetes clusters; attempted creation of a new administrative cloud identity (blocked)
    • Kubernetes API server audit · API calls using service account tokens obtained from other systems; reads of wallet-named Kubernetes secrets
    • Source control audit log · Use of a source-code access token across repositories outside normal developer or CI patterns
  3. Throwaway branches print encoded secrets into build logs

    • T1552.001Unsecured Credentials: Credentials In Files

    Logs

    • GitHub Actions workflow run logs · Short-lived branches pushed to a handful of repositories triggering a build workflow that prints encoded secret values into the job log so the log's secrets masking does not hide them (just under four hours of pushes on November 2)
  4. Read-only container mounts the host file system

    • T1611Escape to Host

    Logs

    • Kubernetes API server audit · Pod created with a read-only hostPath volume mounting the node file system; image not from the release pipeline; deployed outside change windows
    • Container runtime logs · New container in a cluster mounting the node root file system, harvesting the server's credentials
  5. Shell commands hunt for wallet and seed material

    • T1552.001Unsecured Credentials: Credentials In Files
    • T1552.004Unsecured Credentials: Private Keys

    Logs

    • Linux process execution logs · Shell commands searching for environment variables named WALLET, MNEMONIC, SEED and PRIV, Ethereum keystore files, extended private keys and seed phrase files
    • EDR process events · grep and find traversing home directories and Kubernetes secret reads for wallet-named secrets on servers where the attacker had shell access

Sources

Questions, detections or sightings of Barracuda ARTEX cloud intrusion? Bring them to the community.