o0o9 (npm) · Malicious Code
Affects o0o9Source GCVE Database
Malicious package : remove o0o9 and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:18 UTC
Malicious package
Published to npm · OSV MAL-2026-14277
What to do
Remove o0o9 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 |
|---|---|---|
| npmo0o9 | 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 'o0o9' versions 1.8.0 and 2.0.1 contain malicious code that executes a PowerShell process immediately upon import or require on Windows systems. This behavior occurs as a top-level side effect in the package's main entry file, causing unprompted code execution unrelated to any legitimate functionality.
References
- npmjs.com/package/o0o9/v/1.8.0 (opens in a new tab)
- npmjs.com/package/o0o9/v/2.0.1 (opens in a new tab)
- github.com/advisories/GHSA-5f5h-pg84-39h4 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.3 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.3.0 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.7 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.2.1 (opens in a new tab)
- npmjs.com/package/o0o9/v/2.0.0 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.0 (opens in a new tab)
- npmjs.com/package/o0o9/v/2.0.2 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.8 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.8.1 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.4 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.2 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.1.1 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.4.0 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.1 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.6 (opens in a new tab)
- npmjs.com/package/o0o9/v/1.0.9 (opens in a new tab)