Cyber Risks · The Hacker News

npm’s Update to Harden Their Supply Chain, and Points to Consider

Summary: In December 2025, npm completed an authentication overhaul in response to the Sha1-Hulud incident, retiring long-lived classic tokens in favor of credentials that expire quickly and require a second factor for sensitive operations. The article notes that MFA on publish remains optional, so developers can still create 90-day tokens with MFA bypass enabled, and that the original ChalkJS compromise began with an MFA phishing email that tricked a maintainer into sharing a login and one-time password.

What you should know: Access to a maintainer's console still equals the ability to publish new packages and versions, so a successful MFA phishing email yields short-lived tokens that give an attacker the minutes needed to upload malware. The article also cites Chainguard's finding that for 98.5% of malicious npm packages, the malware was absent from the upstream source code and present only in the published artifact.

Read the original at The Hacker News ↗

Topics
Identity & Access Management
Related