Research1 in 10 popular npm releases needed a hotfix

supply chain · malicious package

Malicious code in pxnpm (npm)

Published Oct 9, 2026 · updated Oct 29, 2026

What to do

  1. Check every lockfile and build cache for the affected versions below and remove them.
  2. Rotate any secrets (tokens, keys, cloud credentials) that were available to machines that installed them.
  3. Pin to a known-good version and reinstall from a clean lockfile.

Malicious versions

pxnpm

= 7.0.0-beta.6

Check your project: npm ls pxnpm --all

pxnpm

= 7.0.0-beta.8

Check your project: npm ls pxnpm --all

pxnpm

= 7.0.0

Check your project: npm ls pxnpm --all

pxnpm

= 7.0.1

Check your project: npm ls pxnpm --all

pxnpm

= 7.0.2

Check your project: npm ls pxnpm --all

Sources

← All critical vulnerabilities