nottuff11 (npm) · Malicious Code
Affects nottuff11Source GCVE Database
Malicious package : remove nottuff11 and rotate any secrets on hosts that installed it.
Data as of 12 Sep 2026, 18:17 UTC
Malicious package
Published to npm · OSV MAL-2026-10338
What to do
Remove nottuff11 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 |
|---|---|---|
| npmnottuff11 | 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 npm package 'nottuff11' contains malicious code that facilitates mass publication of nearly 100 misleading package names by rewriting package.json and republishing. It includes a browser Service Worker that serves a heavily obfuscated web proxy frontend with a popunder redirect to an external site. The package does not auto-execute code during Node installation, so the primary harm is registry namespace abuse and browser-side malicious behavior. According to one source, any system with this package installed should be considered fully compromised, with immediate secret/key rotation recommended. Removal of the package alone may not eliminate all resulting malicious software.
References
- github.com/advisories/GHSA-mf3h-3r2x-g3pw (opens in a new tab)
- npmjs.com/package/nottuff11/v/1.7.7 (opens in a new tab)
- npmjs.com/package/nottuff11/v/1.1.7 (opens in a new tab)
- npmjs.com/package/nottuff11/v/2.0.0 (opens in a new tab)
- safedep.io/malicious-npm-terminal3airport-proxy-adware-spam (opens in a new tab)