What does the @spinstorm/shared malware do?

The package @spinstorm/shared was found to contain malicious code. The OpenSSF Package Analysis project identified '@spinstorm/shared' @ 99.99.99 (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 @spinstorm/shared are malicious?

The following npm versions of @spinstorm/shared are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @spinstorm/shared if I installed it?

Remove @spinstorm/shared 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 @spinstorm/shared — how do I know if it already compromised me?

If @spinstorm/shared 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 @spinstorm/shared across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @spinstorm/shared (version 99.99.99).

Malicious package

@spinstorm/sharednpm

Advisory published Apr 22, 2026Updated Apr 23, 2026

@spinstorm/shared is a confirmed malicious npm package (MAL-2026-2998) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @spinstorm/shared (npm)

MAL-2026-2998

Immediate action

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

npm uninstall @spinstorm/shared

What this malware does

The package @spinstorm/shared was found to contain malicious code.

The OpenSSF Package Analysis project identified '@spinstorm/shared' @ 99.99.99 (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

99.99.99

Indicators of compromise (SHA-256)

7dcec109b60aa235a95a55c3035c9e20d01dd36f22c670ab32a5d88b51bd3b70

e56e452f9b6929e66be95ebdf49d432e7bbfeb76fc349123bcc39175f412e802

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @spinstorm/shared-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