What does the black-spindle malware do?

The OpenSSF Package Analysis project identified 'black-spindle' @ 999.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of black-spindle are malicious?

The following npm versions of black-spindle are flagged malicious: 999.0.0. Treat any of these as compromised.

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

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

If black-spindle 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.

How do I find black-spindle across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for black-spindle (version 999.0.0).

Malicious package

black-spindlenpm

Advisory published Oct 28, 2026Updated Oct 28, 2026

black-spindle is a confirmed malicious npm package (MAL-2026-18359) that executes malicious code on install (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in black-spindle (npm)

MAL-2026-18359

Immediate action

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

npm uninstall black-spindle

What this malware does

The OpenSSF Package Analysis project identified 'black-spindle' @ 999.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

c5ef30c4ec24f78fa57d10f6bd8e7fb7be307fc23e833428af785b2013bf2fab

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for black-spindle (version 999.0.0).
If you installed it — respond
Remove black-spindle 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 black-spindle 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 on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks black-spindle-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