sixseven3 (npm) · Malicious Code
Affects sixseven3Source GCVE Database
Malicious package : remove sixseven3 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-10375
What to do
Remove sixseven3 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 |
|---|---|---|
| npmsixseven3 | 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 sixseven3 contains malicious code in the form of a browser ServiceWorker and obfuscated JavaScript assets that serve a proxy site injecting unwanted ads. Installing the package does not execute code on the developer's machine due to browser-only globals, limiting immediate risk to disk usage and registry pollution. However, if the code is deployed in a browser environment, it can proxy cross-origin requests and inject popunder ads. The package is part of a name-squatting batch on npm. According to a malware source, any system with this package installed should be considered fully compromised, and all secrets should be rotated. Removal of the package alone may not eliminate all malicious software.
References
- github.com/advisories/GHSA-rq6j-3wjj-qwrv (opens in a new tab)
- npmjs.com/package/sixseven3/v/1.7.7 (opens in a new tab)
- npmjs.com/package/sixseven3/v/1.1.7 (opens in a new tab)
- npmjs.com/package/sixseven3/v/2.0.0 (opens in a new tab)
- safedep.io/malicious-npm-terminal3airport-proxy-adware-spam (opens in a new tab)