npm

The 0sec-cli npm Malware Advisory

Updated 11 Nov 2026 · Incident date 9 Nov 2026

GitHub flags 0sec-cli 0.28.9 and 0.28.10 as malware. Both releases are now absent from the npm registry.

GitHub published reviewed malware advisory GHSA-9j97-6pqr-qvrx for 0sec-cli on 11 November 2026.

This page reports the advisory and npm registry facts. The removed releases were unavailable for code inspection.

What happened

GitHub classified the package as malware.

  • The updated advisory names 0.28.9 and 0.28.10. It provides no patched version.
  • npm records 0.28.9 on 9 November 2026 and 0.28.10 on 10 November 2026.
  • Both affected releases are absent from the current registry version list. The latest tag now points to 0.28.8.
  • A latest tag is registry metadata. It does not establish that an earlier release is safe.

Affected versions

  • 0.28.9 and 0.28.10, per GitHub advisory GHSA-9j97-6pqr-qvrx.
  • GitHub lists no patched release. This page does not endorse another version as a safe replacement.

How to check

Check your project dependency tree for the package and version. This command reads installed metadata and does not execute the package.

npm ls 0sec-cli

What to do now

GitHub advises treating machines that installed or ran an affected release as compromised.

  1. Remove the affected package.
  2. From a separate computer, rotate secrets and keys stored on the affected machine.
  3. Do not assume package removal removes every malicious component.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `0sec-cli` 0.28.10. This version is too new or changed in a way Vigilance must check first.
The last safe version is 0.28.9. Install that version.

In the owner report

Bad update

0sec-cli 0.28.10

This update now downloads from the internet and runs other programs. The version before it did not.

  1. Ask the AI tool to swap 0sec-cli to 0.28.9. That is the last safe version.

Frequently asked questions

What did the malicious code do?

The advisory gives no payload analysis, and the removed releases were unavailable for inspection. This page does not claim a verified technical mechanism.

Sources

  1. github.com/advisories/GHSA-9j97-6pqr-qvrx
  2. registry.npmjs.org/0sec-cli

More supply chain attacks

All 145 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library