Advisory

GHSA-m5h6-hr3q-22h5

Also known as: CVE-2016-3956

Summary

npm Token Leak in npm

Details

Affected versions of the npm package include the bearer token of the logged in user in every request made by the CLI, even if the request is not directed towards the user's active registry.

An attacker could create an HTTP server to collect tokens, and by various means including but not limited to install scripts, cause the npm CLI to make a request to that server, which would compromise the user's token.

This compromised token could be used to do anything that the user could do, including publishing new packages.

Recommendation

  1. Update npm with npm install npm@latest -g
  2. Revoke your Tokens
  3. Enable Two-Factor Authentication

Severity

High Basis: The source's own band: HIGH

Dates

Published
2018-07-31 22:58 UTC
Modified
2026-09-10 03:47 UTC

Affected packages and fixes

npm

npm · All systems

Affected

  • introduced 0, fixed 2.15.1 (semver)

Fixed versions

2.15.1

Fix

npm

npm · All systems

Affected

  • introduced 3.0.0, fixed 3.8.3 (semver)

Fixed versions

3.8.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences