npm

The @ai-ecoverse/slicc-windows-amd64 npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 20 Oct 2026

GitHub advisory GHSA-38rp-mcrj-j69m lists @ai-ecoverse/slicc-windows-amd64 version 1.46.4 on npm as malware, and npm no longer serves that version.

The package holds the slicc binary for Windows on x86-64. The advisory gives no technical detail, and the code was unavailable for inspection.

What happened

GitHub marked one npm release of the package as malware.

  • Version 1.46.4 went to npm at 2026-10-20T07:40:29.936Z, according to the registry time record.
  • GitHub published and reviewed advisory GHSA-38rp-mcrj-j69m on 4 November 2026. It lists CWE-506, Embedded Malicious Code.
  • The advisory names no file, domain, IP address or hash. It does not say how the bad code reached the release.
  • The registry no longer serves 1.46.4. The version list goes from 1.46.3 to 1.47.0.
  • The registry marks 1.46.3 and 1.49.26 through 1.49.34 as deprecated, with a note that names a security fix in 1.49.35.

The package had 4,436 downloads in the week of 9 to 15 November 2026.

Affected versions

  • @ai-ecoverse/slicc-windows-amd64 1.46.4 on npm.
  • The advisory lists no patched version.
  • Version 1.49.35 carries no deprecation note on the registry.

Indicators of compromise

  • Package and version: @ai-ecoverse/slicc-windows-amd64@1.46.4
  • Advisory: GHSA-38rp-mcrj-j69m

How to check

List the installed version in each project. If the output shows 1.46.4, the machine is affected.

npm ls @ai-ecoverse/slicc-windows-amd64 --all

List the version in your global npm folder.

npm ls -g @ai-ecoverse/slicc-windows-amd64

What to do now

If a machine installed or ran 1.46.4, the advisory says to treat it as fully compromised.

  1. Use a different, clean computer for the next steps.
  2. Rotate every secret and key that the affected machine held.
  3. Remove the package. Removal alone does not prove that the machine is clean.
  4. Pin slicc to version 1.49.35 or later.

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 `@ai-ecoverse/slicc-windows-amd64` 1.46.4. This version is too new or changed in a way Vigilance must check first.
The last safe version is 1.46.3. Install that version.

In the owner report

Bad update

@ai-ecoverse/slicc-windows-amd64 1.46.4

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

  1. Ask the AI tool to swap @ai-ecoverse/slicc-windows-amd64 to 1.46.3. That is the last safe version.

Frequently asked questions

Is @ai-ecoverse/slicc-windows-amd64 safe?

GitHub lists version 1.46.4 as malware. The registry deprecation notes point users to version 1.49.35.

What did @ai-ecoverse/slicc-windows-amd64 1.46.4 do?

The GitHub advisory does not say. npm no longer serves the version, so its code was unavailable for inspection.

Sources

  1. github.com/advisories/GHSA-38rp-mcrj-j69m
  2. registry.npmjs.org/@ai-ecoverse/slicc-windows-amd64

More supply chain attacks

All 147 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