Which versions of 0sec-cli are malicious?

The following npm versions of 0sec-cli are flagged malicious: 0.28.9, 0.28.10. Treat any of these as compromised.

How do I remediate 0sec-cli if I installed it?

Remove 0sec-cli 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 0sec-cli — how do I know if it already compromised me?

If 0sec-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is 0sec-cli part of a known attack campaign?

Yes — 0sec-cli is associated with the GHSA-9j97-6pqr-qvrx 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 0sec-cli across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 0sec-cli (2 malicious versions).

Malicious package

0sec-clinpm

Advisory published Nov 11, 2026Updated Nov 11, 2026

0sec-cli is a confirmed malicious npm package (MAL-2026-19118) that executes malicious code on install (malicious versions 0.28.9, 0.28.10). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 0sec-cli (npm)

MAL-2026-19118

Immediate action

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

npm uninstall 0sec-cli

What this malware does

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

0.28.90.28.10

Indicators of compromise (SHA-256)

6ca0694213fab27d0292d43aee954b81c13e551a81563903fb9afd7e54a9dda2

3c30d9423f714d9676d95618695bba34bd3a5f438a675f388502a9697790ec0b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for 0sec-cli (2 malicious versions).
If you installed it — respond
Remove 0sec-cli 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 0sec-cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. 0sec-cli on npm has been identified as a malicious package (versions 0.28.9, 0.28.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9j97-6pqr-qvrx

References

github.com

Detect & block this

O3 blocks 0sec-cli-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