{
  "id": "barracuda-artex-cloud-key-intrusion-2026-11",
  "name": "Barracuda - an unretired vendor cloud key used in an ARTEX-style intrusion",
  "date_reported": "2026-11-11",
  "date_activity_start": "2026-11-01",
  "date_activity_end": "2026-11-02",
  "researcher": "Arve Kjoelen",
  "org": "Barracuda",
  "sources": [
    {
      "url": "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion",
      "title": "Forty-four hours: Anatomy of a machine-speed intrusion",
      "publisher": "Barracuda"
    },
    {
      "url": "https://trust.barracuda.com/security/barracuda-xdr-integration-credentials",
      "title": "Barracuda XDR integration credentials",
      "publisher": "Barracuda Trust Center"
    },
    {
      "url": "https://www.bleepingcomputer.com/news/security/barracuda-links-cloud-breach-to-artex-ai-powered-cyberattack/",
      "title": "Barracuda links cloud breach to ARTEX AI-powered cyberattack",
      "publisher": "BleepingComputer"
    },
    {
      "url": "https://www.securityweek.com/barracuda-hacked-amid-surge-in-artex-powered-cyberattacks/",
      "title": "Barracuda hacked amid surge in ARTEX-powered cyberattacks",
      "publisher": "SecurityWeek"
    },
    {
      "url": "https://www.ic3.gov/CSA/2026/261113.pdf",
      "title": "FBI FLASH-20261113-001 (CSA 261113): Threat overview of ARTEX. Does not name Barracuda.",
      "publisher": "FBI"
    }
  ],
  "magicsword_coverage": [],
  "borderline": false,
  "borderline_note": null,
  "ai_role": "attacker_uses_ai_as_operator",
  "ai_role_secondary": "ai_credential_theft",
  "ai_role_detail": "Barracuda matches resource names, probe names, order of operations, and built-in credential and wallet hunting to ARTEX. The tool was not recovered, and the match does not identify the operator.",
  "technique_summary": "Barracuda (Arve Kjoelen, CISO; blog Nov 11, 2026, after a Trust Center advisory on Nov 10) describes a cloud intrusion that used a valid access key the company had given a third-party AI vendor and never retired. In October the vendor's development environment was compromised. The Trust Center says the key was stored in a configuration file in that vendor's GitHub repository; other Barracuda credentials in the same file had already expired or were later revoked. First use was Nov 1, 2026 at 04:33 UTC. Within minutes the caller mapped what the key could reach and read secret stores, including AWS access keys and Azure service principal secrets. It decrypted infrastructure-as-code state files and pulled credentials from instance metadata services and Kubernetes service accounts. Over the next day each secret opened the next system: cloud accounts, then a data analytics system, then a source-code access token, then Kubernetes clusters. On Nov 2, in under four hours, short-lived branches were pushed to a handful of repositories so a build workflow printed the build system's secrets into the job log. The secrets were encoded so the log's usual masking would not hide them. Where a shell was obtained, commands searched for environment variables named WALLET, MNEMONIC, SEED, and PRIV, Ethereum keystore files, extended private keys, seed-phrase files, and Kubernetes secrets with wallet-related names. Barracuda says no wallet material was on those systems. For persistence, a container mounted one node's filesystem read-only and harvested that node's credentials. An attempt to create a new administrative cloud identity was blocked. About 10 cloud accounts were touched in roughly 44 hours. Last activity was Nov 2 at 23:31 UTC. An engineer noticed unusual activity on Nov 4, the same day the vendor reported its own incident, and the container was removed that evening Pacific time. Resources were labeled with the letter i followed by digits and no human-readable words. Barracuda says those labels, the probe names, the order of operations, and the built-in credential and wallet routines match ARTEX (https://github.com/RuoJi6/ARTEX). Because many groups use ARTEX, the match describes the method, not a named actor. Barracuda found no direct evidence that Barracuda Managed XDR Cloud or Monitored Endpoint integration credentials were viewed, but logging was not detailed enough to rule it out, and those customers were asked to rotate them. ATT&CK coverage in the write-up is T1552.005 (cloud instance metadata), T1078.004 (valid cloud accounts), T1610 (deploy container), and T1611 (escape to host via the mounted node filesystem). FBI FLASH-20261113-001, CSA 261113 (https://www.ic3.gov/CSA/2026/261113.pdf), is a general ARTEX overview and does not name Barracuda.",
  "initial_access": "Valid cloud access key issued to a third-party AI vendor, left unretired, and later found in a configuration file in the vendor's GitHub repository after that vendor's development environment was compromised in October",
  "ai_tooling_and_models": [
    "ARTEX (https://github.com/RuoJi6/ARTEX); the tool was not recovered"
  ],
  "frameworks": [
    "artex"
  ],
  "other_tooling": [
    "Cloud secret stores, infrastructure-as-code state files, instance metadata, and Kubernetes service accounts",
    "Short-lived Git branches that triggered a build workflow and printed secrets into job logs"
  ],
  "victims_and_sectors": "Barracuda cloud environment, including a data analytics system, source-code access, Kubernetes clusters, and the system that stores Barracuda XDR customer integration credentials. Barracuda says it found no direct evidence those customer credentials were viewed.",
  "regions": [
    "United States"
  ],
  "region_notes": "Barracuda is the named victim. The blog does not state which cloud region the accounts ran in, and it does not name the vendor's country.",
  "attribution_or_cluster": "Unnamed. Barracuda ties the labels, probe names, order of operations, and credential and wallet hunting to ARTEX, and says that match does not identify the operator. The wallet searches are the evidence for a financial motive. AI-service credentials were also in reach; Barracuda does not claim they were the goal.",
  "scale_and_metrics": "About 10 cloud accounts in roughly 44 hours, from Nov 1 04:33 UTC to Nov 2 23:31 UTC. Detected Nov 4, after the activity had stopped.",
  "prevention_angle": "Retire third-party cloud keys when the work ends, and prefer short-lived, narrowly scoped credentials. Do not leave one secret able to read the next store, the source-code token, and the cluster credentials. Alert on bulk secret reads, instance-metadata credential requests, Kubernetes secret lists, a new pod with a hostPath mount, and a new cloud administrator identity. Treat a short-lived branch whose build log prints secrets, especially encoded values that slip past log masking, as a credential-exposure event. Practice rotating every secret in reach, including customer integration keys, without waiting for proof they were read.",
  "related_magicsword_projects": [],
  "source_notes": "Times, the GitHub configuration-file detail, the wallet variable names, the read-only host mount, the blocked administrator identity, and the account count are from the Barracuda blog and Trust Center advisory. The community ARTEX fork is https://github.com/RuoJi6/ARTEX. FBI FLASH-20261113-001 does not name Barracuda; it is cited only so that gap is explicit. Link chainstack-intruder-reached-production-user-password-2026-11, datadog-artex-aws-cognito-2026-11, microsoft-artex-github-secrets-keyvault-2026-11, and eye-security-artex-gitops-2026-11.",
  "last_reviewed": "2026-11-17",
  "iocs": {
    "domains": [],
    "ips": [],
    "hashes": [],
    "urls": []
  },
  "atlas_techniques": [
    {
      "id": "AML.T0055",
      "rationale": "The initial key was left in a vendor repository, and the intrusion read secret stores, infrastructure-as-code state, instance metadata, and Kubernetes service accounts.",
      "source_urls": [
        "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion",
        "https://trust.barracuda.com/security/barracuda-xdr-integration-credentials"
      ]
    },
    {
      "id": "AML.T0012",
      "rationale": "The first calls used a still-valid cloud access key issued to the vendor.",
      "source_urls": [
        "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
      ]
    },
    {
      "id": "AML.T0053",
      "rationale": "Barracuda attributes the probe order and the built-in credential and wallet routines to ARTEX's planner and worker agents. The tool was not recovered.",
      "source_urls": [
        "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
      ]
    },
    {
      "id": "AML.T0025",
      "rationale": "Secrets were carried out by follow-on use of stolen keys and by a build log that printed encoded secret values.",
      "source_urls": [
        "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
      ]
    }
  ],
  "attack_flow": {
    "nodes": [
      {
        "id": "vendor-key",
        "title": "Unretired vendor key",
        "description": "A cloud access key given to an AI vendor was never retired. After the vendor's October compromise, the key was in a configuration file in the vendor's GitHub repository.",
        "kind": "access",
        "source_urls": [
          "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion",
          "https://trust.barracuda.com/security/barracuda-xdr-integration-credentials"
        ]
      },
      {
        "id": "secret-chain",
        "title": "Secrets open the next system",
        "description": "From Nov 1 04:33 UTC the key reads secret stores, infrastructure-as-code state, instance metadata, and Kubernetes service accounts, then reaches analytics, a source-code token, and clusters.",
        "kind": "execution",
        "source_urls": [
          "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
        ]
      },
      {
        "id": "artex-match",
        "title": "ARTEX fingerprints, tool not recovered",
        "description": "Resources named with i plus digits, probe names, the order of operations, and wallet hunting match ARTEX. Barracuda did not recover the tool and does not name the operator.",
        "kind": "ai",
        "source_urls": [
          "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
        ]
      },
      {
        "id": "ci-and-mount",
        "title": "CI logs and a host mount",
        "description": "On Nov 2, short-lived branches make a build workflow print encoded secrets into job logs. A read-only host filesystem mount harvests node credentials. A new cloud administrator identity is blocked.",
        "kind": "impact",
        "source_urls": [
          "https://blog.barracuda.com/2026/11/11/anatomy-of-a-machine-speed-intrusion"
        ]
      }
    ],
    "edges": [
      {
        "source": "vendor-key",
        "target": "secret-chain"
      },
      {
        "source": "secret-chain",
        "target": "artex-match"
      },
      {
        "source": "secret-chain",
        "target": "ci-and-mount"
      }
    ]
  },
  "category": "adversary-use-of-ai",
  "attribution": {
    "actor_name": "Unnamed",
    "country": "Unknown",
    "motivation": "financially-motivated",
    "attributed_by": "Barracuda (Arve Kjoelen, CISO)",
    "confidence": "low"
  },
  "ai_involvement_confidence": "vendor-asserted",
  "detections": [
    {
      "name": "Kubernetes Pod Created with a Sensitive hostPath Volume",
      "format": "elastic",
      "url": "https://github.com/elastic/detection-rules/blob/main/rules/integrations/kubernetes/privilege_escalation_pod_created_with_sensitive_hostpath_volume.toml",
      "notes": "Selected from a security-detections-mcp search for hostPath. Kubernetes audit. A new pod whose volume mounts a sensitive path from the node. Matches the container Barracuda described mounting the node filesystem, including a read-only mount."
    },
    {
      "name": "Container With A hostPath Mount Created",
      "format": "sigma",
      "url": "https://github.com/SigmaHQ/sigma/blob/master/rules/application/kubernetes/audit/kubernetes_audit_hostpath_mount.yml",
      "notes": "Selected from a security-detections-mcp search for hostPath. Kubernetes audit create of a pod with any hostPath volume. Low severity because DaemonSets also use hostPath."
    },
    {
      "name": "Kubernetes Pod Exec Cloud Instance Metadata Access",
      "format": "elastic",
      "url": "https://github.com/elastic/detection-rules/blob/main/rules/integrations/kubernetes/credential_access_kubernetes_pod_exec_cloud_instance_metadata.toml",
      "notes": "Selected from a security-detections-mcp search for cloud instance metadata. Kubernetes audit of pod exec commands that reference instance-metadata endpoints. Covers credential reads from the node metadata service during an exec. It does not cover a metadata call made only by the kubelet or by a process that never appears in the exec command line."
    },
    {
      "name": "AWS Secrets Manager Rapid Secrets Retrieval",
      "format": "elastic",
      "url": "https://github.com/elastic/detection-rules/blob/main/rules/integrations/aws/credential_access_rapid_secret_retrieval_attempts_from_secretsmanager.toml",
      "notes": "Selected from a security-detections-mcp search for GetSecretValue. AWS CloudTrail. Twenty or more distinct GetSecretValue or BatchGetSecretValue calls by one identity in a short window. Barracuda described secret-store reads that included AWS access keys. This rule does not cover Azure service principal secret reads."
    },
    {
      "name": "Kubernetes Secrets Enumeration",
      "format": "sigma",
      "url": "https://github.com/SigmaHQ/sigma/blob/master/rules/application/kubernetes/audit/kubernetes_audit_secrets_enumeration.yml",
      "notes": "Selected from a security-detections-mcp search for Kubernetes secrets. Kubernetes audit list on the secrets resource, which is how a caller inventories service-account tokens and wallet-named secrets."
    },
    {
      "name": "AWS IAM AdministratorAccess Policy Attached to User",
      "format": "elastic",
      "url": "https://github.com/elastic/detection-rules/blob/main/rules/integrations/aws/privilege_escalation_iam_administratoraccess_policy_attached_to_user.toml",
      "notes": "Selected from a security-detections-mcp search for AdministratorAccess. AWS CloudTrail AttachUserPolicy of AdministratorAccess. Barracuda says a new administrative cloud identity was blocked and does not name the API. A denied call may not match a successful attach. There is no cited rule for the blocked attempt itself."
    },
    {
      "name": "CI log secret dump and i-plus-digits names",
      "format": "guidance",
      "notes": "security-detections-mcp search for GitHub workflow returned GitHub Workflow File Creation or Modification, an endpoint hunt for .github/workflows files on a workstation. Barracuda describes short-lived branches that triggered an existing build workflow so the job log printed encoded secrets. That push is not a local workflow-file write, so the endpoint rule is not cited. Hunt the git host for short-lived branches and for job logs that contain encoded secret material. Also hunt resource names that are the letter i followed only by digits. No cited rule covers Azure service principal secret reads."
    }
  ],
  "timeline": {
    "first_seen": "2026-11-01",
    "last_updated": "2026-11-13",
    "updates": [
      {
        "date": "2026-10-01",
        "source": "Barracuda",
        "summary": "October, day not stated: the AI vendor's development environment is compromised. The Barracuda key is later found in a configuration file in the vendor's GitHub repository."
      },
      {
        "date": "2026-11-01",
        "source": "Barracuda",
        "summary": "04:33 UTC first use of the key. Secret stores, infrastructure-as-code state, instance metadata, and Kubernetes service accounts are read, and the chain continues into analytics, source code, and clusters."
      },
      {
        "date": "2026-11-02",
        "source": "Barracuda",
        "summary": "Short-lived branches make a build workflow print encoded secrets into job logs. A read-only host mount is deployed. A new cloud administrator identity is blocked. Last activity 23:31 UTC."
      },
      {
        "date": "2026-11-04",
        "source": "Barracuda",
        "summary": "An engineer reports unusual account activity. The vendor shares its own incident the same day. The container is removed that evening Pacific time."
      },
      {
        "date": "2026-11-10",
        "source": "Barracuda Trust Center",
        "summary": "Trust Center advisory on XDR integration credentials. Customers who may be affected are asked to revoke and recreate them."
      },
      {
        "date": "2026-11-11",
        "source": "Barracuda",
        "summary": "Arve Kjoelen publishes the 44-hour narrative and the ARTEX fingerprint match."
      },
      {
        "date": "2026-11-13",
        "source": "FBI",
        "summary": "FLASH-20261113-001 (CSA 261113) summarizes ARTEX activity. It does not name Barracuda."
      }
    ]
  }
}