Npmjs Npm any version

The npm ci command in npm 7.x and 8.x through 8.1.3 proceeds with an installation even if dependency information in package-lock.json differs from package.json. This behavior is inconsistent with the documentation, and makes it easier for attackers to install malware that was supposed to have been blocked by an exact version match requirement in package-lock.json. NOTE: The npm team believes this is not a vulnerability. It would require someone to socially engineer package.json which has different dependencies than package-lock.json. That user would have to have file system or write access to change dependencies. The npm team states preventing malicious actors from socially engineering or gaining file system access is outside the scope of the npm CLI.

UNIX Symbolic Link (Symlink) Following in @npmcli/arborist

UNIX Symbolic Link (Symlink) Following in @npmcli/arborist

Unauthorized File Access in npm CLI before before version 6.13.3

Unauthorized File Access in npm CLI before before version 6.13.3

Arbitrary File Overwrite in npm CLI

The CLI in npm before 2.15.1 and 3.x before 3.8.3, as used in Node.js 0.10 before 0.10.44, 0.12 before 0.12.13, 4 before 4.4.2, and 5 before 5.10.0, includes bearer tokens with arbitrary requests, which allows remote HTTP servers to obtain sensitive information by reading Authorization headers.

npm packing does not respect root-level ignore files in workspaces

Sensitive information exposure through logs in npm cli