Skip to main content
HighContentOWASP A07:2021CWE-798

How to fix: NPM Token Exposed

NPM authentication token found.

Why it matters

Package publishing, supply chain attack.

NPM tokens allow package publishing.

How to fix it

  1. 1Revoke token, publish with 2FA.

Code examples

Revoke exposed npm token

bash
# List tokens:
npm token list

# Revoke the compromised token:
npm token revoke <token-id>

# Create a new scoped token:
npm token create --read-only  # for CI install
npm token create              # for publishing

# Check for unauthorized publishes:
npm view your-package versions --json

References

Detected automatically by VulnRadar. The check id is npm-token-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is NPM Token Exposed?
VulnRadar rates this high severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id npm-token-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does NPM Token Exposed map to?
It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for npm token exposed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: NPM Token Exposed | VulnRadar