The attack
On the morning of Tuesday, August 4, 2026 (US time), Socket and Wiz researchers saw an npm supply-chain attack begin in the keyv and cacheable namespaces after the apparent compromise of maintainer account Jaredwray. The packages have tens of millions of weekly downloads, often indirectly (e.g. eslint → file-entry-cache → flat-cache → keyv).
How the malware spreads
Malicious versions use a preinstall hook that downloads a Bun runtime and runs Math_Symbol.js. The payload steals AWS/GCP/Azure keys, Vault/Kubernetes/GitHub OIDC tokens and npm tokens, runs a TruffleHog-style sweep and spreads by republishing other packages with stolen tokens. Data is encrypted (AES-256-GCM) and sent to GitHub repos titled "Shai-Hulud: Here We Go Again", plus .claude and .vscode hooks.
What to do
Pin clean versions, rebuild lockfiles, audit npm/GitHub accounts and rotate cloud credentials. Remove malicious loaders before rotating tokens, because of a dead-man’s switch that polls the GitHub API every 60 seconds.