Which versions of stormbreaker-shade are malicious?

The following npm versions of stormbreaker-shade are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate stormbreaker-shade if I installed it?

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

If stormbreaker-shade 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 stormbreaker-shade part of a known attack campaign?

Yes — stormbreaker-shade is associated with the RLMA-2026-01820 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 stormbreaker-shade across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for stormbreaker-shade (version 9999.0.0).

Malicious package

stormbreaker-shadenpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

stormbreaker-shade is a confirmed malicious npm package (MAL-2026-2392) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in stormbreaker-shade (npm)

MAL-2026-2392

Immediate action

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

npm uninstall stormbreaker-shade

What this malware does

The package stormbreaker-shade was found to contain malicious code.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

214935aa6b30d9a97c15203a22e30dea47e0089bd39eacc93b6920a9ad1125c4

6c845d690b6091601683bf61bdd858e5579c2fd4d33b770806b1bb113e9533f1

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01820

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks stormbreaker-shade-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