← All playbooks
HighBreach · 2026-11-16

Barracuda cloud breach: unrevoked AI-vendor access key let an ARTEX-style intruder roam 10 cloud accounts for 44 hours

SockAnalyst · Security+ certified analyst.

What happened

Barracuda says an attacker used a valid cloud access key it had issued to a third-party AI vendor and never retired after the project ended. The key sat in a configuration file in the vendor's GitHub repository and was exposed when the vendor's own development environment was compromised in October. The attacker's first call with the key was at 04:33 UTC on November 1, 2026 and the last recorded activity was 23:31 UTC on November 2: about 44 hours across roughly 10 cloud accounts. It read secret stores (AWS access keys, Azure service principal secrets), decrypted infrastructure-as-code state files, pulled credentials from instance metadata and Kubernetes service accounts, moved into a data-analytics system, a source-code access token and Kubernetes clusters, and pushed short-lived branches to trigger a build workflow that printed CI secrets into job logs in encoded form so masking would not hide them. It also searched servers for crypto wallets (WALLET, MNEMONIC, SEED, PRIV variables, Ethereum keystores, seed phrases). One reached system stores the credentials Barracuda XDR uses to pull data from customers' Microsoft 365, Google Workspace and endpoint tools; Barracuda found no direct evidence they were viewed but could not rule it out, so it notified affected customers. Barracuda says the naming patterns and routines match the ARTEX AI penetration-testing framework, which tells how the attacker worked, not who it was. Barracuda says the ESG flaws it patched the same week do not appear to have been used.

Who's affected

Barracuda Managed XDR Cloud and Monitored Endpoint customers that use an API integration and received a notification from Barracuda. Organizations not notified, or not using either integration, are not required to act. The broader lesson applies to any organization that has handed long-lived cloud keys to vendors.

✅ Fix / patch

  • If Barracuda notified you: revoke and recreate the XDR integration credentials (Microsoft 365, Google Workspace, EDR and other connected services) using the Barracuda Campus guidance, then review activity in those connected systems from November 1, 2026 onward. Questions go to [email protected].
  • Check your own logs for the IPs and user agents Barracuda published (listed below), remembering they may be shared or reassigned infrastructure.
  • Inventory every cloud access key, service principal secret and token you have issued to vendors and contractors; expire anything tied to a finished engagement and prefer short-lived, scoped credentials.
  • Harden CI: block secrets from being printed to logs in any encoding, require review before new branches can run workflows that read secrets, and restrict which Kubernetes service accounts can read secrets or run privileged pods that mount the host file system.

🔎 Quick hunt check

Barracuda published IOCs: four IPs and five user agents (below), plus naming patterns: cloud and Kubernetes resources named the letter i followed by digits with no hyphen (for example i31911, i28324probe, i19engx1), and GitHub workflow files i19ghci.yml and i19ci2.yml on branches starting i19ghci- or i19ci2-. Barracuda notes these alone do not confirm malicious activity. Hunt CloudTrail/Azure activity and Entra sign-ins for the IPs and user agents, Kubernetes audit and cloud resource creation for i+digits names, GitHub audit logs for those workflow files and branch names, and shell commands grepping for WALLET, MNEMONIC, SEED or keystore files.

MITRE ATT&CK: T1078.004, T1552.005, T1552.001, T1528, T1609, T1213.003

IOCs

  • IP addresses: 180.178.56[.]10, 52.128.238[.]126, 221.146.68[.]107, 2a09:bac1:7680:3d0::26b:5b
  • Files / paths: User agents: Boto3/1.43.122; curl/8.5.0; curl/7.81.0; Python-urllib/3.10; Mozilla/5.0 (compatible; read-only-audit), Cloud/Kubernetes resource names: letter i + digits, no hyphen (e.g. i31911, i28324probe, i19engx1), GitHub workflow files i19ghci.yml and i19ci2.yml on branches beginning i19ghci- / i19ci2-

IOCs from Barracuda's advisory. Barracuda says presence of these indicators does not by itself confirm malicious activity; the IPv6 address is listed as published. The curl and Python-urllib user agents are common and need context.

Hunt queries

Starting points built only from published indicators. Field names vary; tune before use.

index=* earliest=10/31/2026:00:00:00
(sourcetype=aws:cloudtrail OR sourcetype=azure:* OR sourcetype=mscs:* OR sourcetype=o365:* OR sourcetype=*kube* OR sourcetype=github* OR sourcetype=*linux* OR sourcetype=*sysmon* OR sourcetype=*edr*)
("180.178.56.10" OR "52.128.238.126" OR "221.146.68.107" OR "2a09:bac1:7680:3d0::26b:5b" OR "Boto3/1.43.122" OR "read-only-audit" OR "i19ghci" OR "i19ci2" OR "MNEMONIC" OR "keystore" OR "curl/8.5.0" OR "curl/7.81.0" OR "Python-urllib/3.10")
| eval src=coalesce(sourceIPAddress, src_ip, src, actor_ip, ipAddress), ua=coalesce(userAgent, user_agent, http_user_agent)
| eval signal=case(in(src,"180.178.56.10","52.128.238.126","221.146.68.107","2a09:bac1:7680:3d0::26b:5b"),"barracuda_ioc_ip", match(ua,"read-only-audit|^Boto3/1\.43\.122"),"barracuda_ioc_user_agent", match(_raw,"i19ghci|i19ci2"),"artex_style_workflow_or_branch", match(_raw,"(?i)(grep|env|printenv|find).*(WALLET|MNEMONIC|SEED|PRIV|keystore)"),"wallet_hunting_command", match(ua,"^(curl/8\.5\.0|curl/7\.81\.0|Python-urllib/3\.10)$") AND isnotnull(src),"ioc_user_agent_review", true(),null())
| where isnotnull(signal)
| stats count min(_time) as first_seen max(_time) as last_seen values(signal) as signals values(ua) as user_agents values(src) as sources by sourcetype, host
| sort - count
// Barracuda cloud breach (Nov 1-2, 2026): Barracuda-published IPs/user agents, i19ghci/i19ci2 workflows, wallet-hunting commands. curl/Python-urllib agents are common; review in context.
let BadIPs = dynamic(["180.178.56.10", "52.128.238.126", "221.146.68.107", "2a09:bac1:7680:3d0::26b:5b"]);
let BadUAs = dynamic(["Boto3/1.43.122", "Mozilla/5.0 (compatible; read-only-audit)"]);
let Since = datetime(2026-10-31);
union isfuzzy=true
(SigninLogs | where TimeGenerated >= Since | where IPAddress in (BadIPs) or UserAgent in (BadUAs) | extend Signal = "entra_signin_ioc", Who = UserPrincipalName, Evidence = strcat(IPAddress, " ", UserAgent)),
(AADServicePrincipalSignInLogs | where TimeGenerated >= Since | where IPAddress in (BadIPs) | extend Signal = "service_principal_ioc_ip", Who = ServicePrincipalName, Evidence = IPAddress),
(AzureActivity | where TimeGenerated >= Since | where CallerIpAddress in (BadIPs) or (OperationNameValue has "write" and tostring(Properties) matches regex @"/i\d{3,}[a-z0-9]*\b") | extend Signal = "azure_activity", Who = Caller, Evidence = strcat(CallerIpAddress, " ", OperationNameValue)),
(AWSCloudTrail | where TimeGenerated >= Since | where SourceIpAddress in (BadIPs) or UserAgent in (BadUAs) | extend Signal = "cloudtrail_ioc", Who = UserIdentityArn, Evidence = strcat(SourceIpAddress, " ", EventName, " ", UserAgent)),
(DeviceProcessEvents | where TimeGenerated >= Since | where ProcessCommandLine has_any ("MNEMONIC", "keystore", "i19ghci", "i19ci2") and ProcessCommandLine has_any ("grep", "find", "env", "printenv", "git") | extend Signal = "wallet_hunt_or_workflow", Who = AccountName, Evidence = ProcessCommandLine)
| summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Signals = make_set(Signal), Evidence = make_set(Evidence, 20) by Who
| order by Hits desc
// Barracuda cloud breach (Nov 1-2, 2026): published IPs/user agents, i+digits resource names, i19ghci/i19ci2 workflows, wallet-hunting commands

See all hunt queries →

⏱ CISA deadline

Not in CISA KEV as of Nov 18, 2026.

Sources

Related playbooks

Get the SockAnalyst Weekly Brief free, every Thursday.

One email a week with the KEV deadlines, patches and hunt queries that matter. New playbooks still post here on the site every morning.

Subscribe free

Read the free weekly pack →