Barracuda: attacker used a cloud key left with an AI vendor to move through about 10 cloud accounts in 44 hours; some XDR customers told to recreate integration credentials
- Notified Barracuda customers: revoke and recreate XDR integration credentials and review connected-system activity since Nov 1, 2026.
- IOCs (Barracuda): 180.178.56.10, 52.128.238.126, 221.146.68.107, 2a09:bac1:7680:3d0::26b:5b; 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 resources named 'i' plus digits (e.g.i31911,i28324probe); GitHub workflowsi19ghci.yml/i19ci2.ymlon branches startingi19ghci-/i19ci2-. - Lesson: expire every key you hand to a vendor when the engagement ends, and alert on CI runs from short-lived branches that touch secrets.
Sources: Barracuda Trust Center: Barracuda XDR Integration Credentials (Nov 10, updated Nov 13, 2026) · Barracuda blog (Arve Kjoelen): Forty-four hours: Anatomy of a machine-speed intrusion (Nov 11, 2026)