Important npm Security Updates: Token Management and Auth Changes
Blog post from SSOJet
npm has revoked all classic tokens as of December 9, 2025, replacing them with short-lived, two-hour session tokens from npm login and encouraging users to adopt granular access tokens or OIDC trusted publishing. New package publications enforce two-factor authentication by default, while write-capable granular tokens now require 2FA unless a CI-specific bypass is enabled and are limited to a maximum 90-day lifespan. npm has also added CLI commands for creating, listing, and revoking granular tokens, temporarily restored a legacy API endpoint that issues session tokens for compatibility with tools such as Yarn v1 and v2, and recommends migration before that endpoint is removed. New TOTP-based 2FA enrollment is disabled in favor of WebAuthn and passkeys, although existing TOTP configurations will temporarily remain functional. The guidance outlines migration options for local development, CI/CD, and GitHub Actions or GitLab CI/CD workflows, while also noting common publishing and installation failures caused by revoked credentials, expired tokens, incomplete OIDC package configuration, or outdated CI images.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.