Which versions of black-spindle-2 are malicious?

The following npm versions of black-spindle-2 are flagged malicious: 100.0.0, 301.0.0. Treat any of these as compromised.

How do I remediate black-spindle-2 if I installed it?

black-spindle-2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed black-spindle-2 — how do I know if it already compromised me?

If black-spindle-2 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 black-spindle-2 part of a known attack campaign?

Yes — black-spindle-2 is associated with the IN-MAL-2026-022416, IN-MAL-2026-022417 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 black-spindle-2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for black-spindle-2 (2 malicious versions).

Malicious package

black-spindle-2npm

Advisory published Oct 29, 2026Updated Oct 29, 2026

black-spindle-2 is a confirmed malicious npm package (MAL-2026-18376) that steals credentials and exfiltrates sensitive data (malicious versions 100.0.0, 301.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in black-spindle-2 (npm)

MAL-2026-18376

Immediate action

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

npm uninstall black-spindle-2

What this malware does

package.json declares a postinstall script that runs curl against the ephemeral host http://778e-181-63-25-28.ngrok-free.app over plain HTTP, embedding a shell command-substitution expression in the URL path. The script fires automatically on npm install, confirming installation on the installer's machine and providing a channel to exfiltrate host or environment values via the expanded shell expression. The shipped index.js is an empty stub, so the manifest's postinstall beacon is the package's entire effect. The destination is an anonymous ngrok-free.app tunnel with no relationship to any legitimate publisher, consistent with a dependency-confusion or install-confirmation probe.

Malicious versions

2 flagged

100.0.0301.0.0

Indicators of compromise (SHA-256)

433228fbed18f3104fed4cd1bce59bc5a76b8ea061d18c8fc9516c92b6b26e90

f973afbbc02414b7152e990c158f7ede82cfc71a14c99ece0b714b57e50b2a55

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for black-spindle-2 (2 malicious versions).
If you installed it — respond
black-spindle-2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If black-spindle-2 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. black-spindle-2 on npm has been identified as a malicious package (versions 100.0.0, 301.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022416IN-MAL-2026-022417

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks black-spindle-2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database