• Sources: discussion
  • Summary: SecurityWeek reports that Barracuda disclosed an intrusion on 2026-11-01 and 2026-11-02 in which an attacker used an exposed valid cloud access key, then reused secrets found in secret stores, configurations, Kubernetes service accounts and metadata services to spread. Barracuda says the probe names and order of work match the Artex framework, the attacker hunted crypto wallet files on shelled servers, and a backdoor was left in a Kubernetes cluster. Barracuda compares it to the October Railway intrusion and has not attributed it.
  • Why it matters: A single leaked cloud key is enough for an agent to walk secret stores and service accounts across accounts, so key scoping and secret sprawl in Kubernetes are the controls to check.