npm Access Token Exposed
An npm access token is public. If it can publish, an attacker can push a malicious version of any package you own — and every project that installs or updates it executes that code. This is a supply-chain compromise: the damage extends to your users' machines and CI systems, not just your own.
Why it matters
An npm access token is public. If it can publish, an attacker can push a malicious version of any package you own — and every project that installs or updates it executes that code. This is a supply-chain compromise: the damage extends to your users' machines and CI systems, not just your own.
How ShipReady detects it
Detects credentials that reached the browser. Scans the page HTML and every linked JavaScript bundle for the literal shapes real provider keys take — `sk_live_`, `AKIA`, `ghp_`, a JWT with a service_role claim — rather than guessing from entropy. High-entropy string detection finds build hashes, CSS class names and base64 images on almost every site; provider prefixes are unambiguous, which is why this check reports only what it can name. A match is evidence, not inference: the value was served to anyone who loaded the page. Evidence records the variable NAME and a ten-character prefix, never the key, because a report that quoted the secret would republish it. Bundles are fetched once per scan and shared across pages, so a key present in a chunk loaded on ten routes is reported once.
Detection is deterministic. ShipReady reports this only when it observes the condition directly, and prefers to miss a real problem over inventing one. Rule version 1.4.0.
How to fix it
This is the prompt ShipReady puts in your report — written to be pasted straight into Cursor, Claude Code, or whichever assistant built the app.
Revoke this token now at npmjs.com -> Access Tokens, and check your packages' version history for releases you did not publish. Use granular access tokens scoped to specific packages, store them only in CI secrets, and enable two-factor authentication for publishing so a leaked token alone cannot ship a release.
Frequently asked questions
- What does "npm Access Token Exposed" mean?
- An npm access token is public. If it can publish, an attacker can push a malicious version of any package you own — and every project that installs or updates it executes that code. This is a supply-chain compromise: the damage extends to your users' machines and CI systems, not just your own.
- How serious is it?
- ShipReady rates this critical. Fix before launch. On its own, this is enough to compromise the application.
- How do I fix it?
- Paste the fix prompt on this page into Cursor, Claude Code or your AI editor. It is the same prompt ShipReady puts in your report.
- Can I check my own site?
- Yes — ShipReady scans up to ten pages of any public site for free and reports this alongside every other check.
Related checks
Does your site have this?
ShipReady checks this and 73 other things across up to ten pages of your site. Free, no signup.
Scan my site