nano-perf (npm) · Malicious Code
Affects nano-perfSource GCVE Database
Malicious package : remove nano-perf and rotate any secrets on hosts that installed it.
Data as of 20 Aug 2026, 14:29 UTC
Malicious package
Published to npm · OSV MAL-2026-11204
What to do
Remove nano-perf from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnano-perf | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The nano-perf npm package versions 1.0.0 through 2.2.0 contain malicious code that installs a persistent background daemon during installation. This daemon silently collects system fingerprint and telemetry data and periodically sends it encrypted to a remote command-and-control server. It also polls for remote tasks to execute, including CPU benchmarking and system probing. The package advertises itself as a performance monitoring tool but does not disclose this covert behavior. Systems with this package installed should be considered fully compromised.
References
- npmjs.com/package/nano-perf/v/2.2.0 (opens in a new tab)
- github.com/ossf/malicious-packages/issues/1373 (opens in a new tab)
- github.com/advisories/GHSA-4236-g67q-42fc (opens in a new tab)
- npmjs.com/package/nano-perf/v/2.0.1 (opens in a new tab)
- npmjs.com/package/nano-perf/v/2.1.0 (opens in a new tab)
- npmjs.com/package/nano-perf/v/2.0.0 (opens in a new tab)
- npmjs.com/package/nano-perf/v/1.0.1 (opens in a new tab)
- npmjs.com/package/nano-perf/v/1.1.0 (opens in a new tab)
- npmjs.com/package/nano-perf/v/1.0.0 (opens in a new tab)