After the npm Hack: We Need Real Package Management—But We Won’t Do It
We know how to fix JavaScript’s dependency mess, but the industry will choose symbolic gestures over real reforms.
We know how to fix JavaScript’s dependency mess, but the industry will choose symbolic gestures over real reforms.

A shared repo’s GitHub Actions secret was exfiltrated via a malicious workflow, enabling malicious npm publishes; the author has locked down publishing now and is moving toward OIDC to eliminate static tokens.
Microsoft’s control of npm hasn’t fixed its core weaknesses, leaving the JavaScript supply chain dangerously insecure and enterprises exposed.

A self-propagating npm attack backdoored @ctrl/tinycolor and 40+ packages to steal multi-cloud and GitHub secrets, persist via Actions workflows, and exfiltrate data—demanding immediate removal, credential rotation, and CI/CD hardening.