GitHub Mandates 2FA and Short-Lived Tokens to Strengthen npm Supply Chain Security
Summary: GitHub announced it will change its authentication and publishing options in response to a wave of npm supply chain attacks, including Shai-Hulud, adding local publishing with required 2FA, granular tokens limited to a seven-day lifetime, and trusted publishing via OpenID Connect that authenticates each publish with short-lived, workflow-specific credentials and generates provenance attestations. The Shai-Hulud worm, disclosed a week earlier, injected self-replicating code into hundreds of npm packages and scanned developer machines for secrets sent to an attacker-controlled server, while Socket separately reported the npm package fezbox, downloaded 476 times since August 21, 2025, which fetched a QR code to execute an obfuscated payload that read document.cookie and posted credentials to an external server.
What's compelling: Shai-Hulud stole multiple types of secrets, not just npm tokens, and GitHub's Xavier René-Corail said it could have enabled an endless stream of attacks without timely action from GitHub and open source maintainers. A seven-day token lifetime and OIDC-based publishing only help if your pipelines stop relying on long-lived credentials that a worm on a developer machine can lift.
Read the original at The Hacker News ↗
- Topics
- Supply Chain & AppSec
- Related
- Kitesurf is now open source Cyber Risks · Nov 13, 2026Trained to betray: How post-training supply chain attacks hijack coding agents Cyber Risks · Nov 12, 2026ZDI-26-913: (0Day) Meta fairseq load_audio_path Code Injection Remote Code Execution Vulnerability Cyber Risks · Nov 11, 2026