npm Adds 2FA-Gated Publishing and Package Install Controls Against Supply Chain Attacks
Summary: GitHub made staged publishing generally available on npm, requiring a human maintainer to pass a 2FA challenge before a prebuilt tarball moves from a stage queue to npmjs.com and becomes installable. It also added three new install source flags alongside the existing -allow-git flag, applying an explicit-allowlist approach to every non-registry install source, with the npm stage publish command requiring npm CLI 11.15.0 or newer.
What you should know: The change lands as one cybercriminal group, TeamPCP, is poisoning popular packages at unprecedented scale through a self-perpetuating cycle of compromises - and staged publishing only helps if maintainers adopt it and pair it with OIDC trusted publishing.
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