Forty-four hours: Anatomy of a machine-speed intrusion · Arve Kjoelen, CISO, Barracuda · Barracuda blog, November 11, 2026
Barracuda's 44-hour timeline of an agent-driven intrusion
The attacker came in with a valid cloud access key that Barracuda had given an AI vendor and never retired. Barracuda believes the key was found when the vendor's own development environment was compromised in October, and writes: "That is on us." From the first call at 04:33 UTC on November 1, the attacker read stored secrets and moved from Barracuda's cloud accounts into a data analytics system, then a source-code access token, then Kubernetes clusters, touching about 10 cloud accounts in roughly 44 hours. In one step it pushed short-lived branches to trigger a build workflow written to print the build system's secrets into the job log, encoded so the log's secrets masking would not hide them. Barracuda matched the probe names, the order of operations and the credential- and wallet-hunting routines to ARTEX, and notes that the match "tells us how the attacker operated, not who it was." The activity had already stopped when an engineer reported something unusual on November 4. Kjoelen's conclusion: "Detect-and-respond, as the primary strategy, is dead."
Why it matters: The weak points in this timeline are ones most software factories also have: a long-lived key held by a third party, and a CI workflow that a pushed branch could run and turn into a secrets dump. Barracuda says short-lived, narrowly scoped credentials would have stopped the intrusion at its first step, so standing keys held by vendors, agents and pipelines are the place to start looking.