Which versions of o0o9 are malicious?

The following npm versions of o0o9 are flagged malicious: 1.8.0, 2.0.1. Treat any of these as compromised.

How do I remediate o0o9 if I installed it?

Remove o0o9 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed o0o9 — how do I know if it already compromised me?

If o0o9 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is o0o9 part of a known attack campaign?

Yes — o0o9 is associated with the IN-MAL-2026-018390, IN-MAL-2026-018389 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find o0o9 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for o0o9 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging o0o9 across your stack and pipelines.

Malicious package

o0o9npm

o0o9 is a confirmed malicious npm package (MAL-2026-14277) that executes malicious code on install (malicious versions 1.8.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in o0o9 (npm)

MAL-2026-14277

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall o0o9

What this malware does

The package's main entry index.js imports child_process at the top of the file and invokes spawn("powershell",...) as a top-level side effect (line 27). Loading the module via require/import causes an unprompted PowerShell process to launch on the installer's machine, which is a Windows-focused code execution vector wholly unrelated to any legitimate library function. This is the shape of an install/import-time execution payload rather than an API a caller must opt into.

Malicious versions

2 flagged

1.8.02.0.1

Indicators of compromise (SHA-256)

a1d425848ef7172faf5f84ff9bd9017bf3ab1eb2343a5301ff0df1711d091118

dc07d1bcb92034037f41bf30cf6bd67f5313276df6aeef3a805d4b52d757e22b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for o0o9 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging o0o9 across your stack and pipelines.
If you installed it — respond
Remove o0o9 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If o0o9 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks o0o9 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. o0o9 on npm has been identified as a malicious package (versions 1.8.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018390IN-MAL-2026-018389

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks o0o9-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database