Which versions of @spinstorm/derng are malicious?

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

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

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

If @spinstorm/derng 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 @spinstorm/derng part of a known attack campaign?

Yes — @spinstorm/derng is associated with the RLMA-2026-04781, RLUA-2026-05928 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 @spinstorm/derng across my projects, lockfiles, and CI pipelines?

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

Malicious package

@spinstorm/derngnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@spinstorm/derng is a confirmed malicious npm package (MAL-2026-7090) 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/derng (npm)

MAL-2026-7090

Immediate action

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

npm uninstall @spinstorm/derng

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

02c200c88334d2787e5095a81f3cfd062d61b00ed63af1251e400da26abe21be

b16659a3599a2c262322b24734ec6b777a3fc8ccc628a30fea1e189e538ef355

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @spinstorm/derng (version 99.99.99).
If you installed it — respond
Remove @spinstorm/derng 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/derng 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/derng 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.

Campaign

RLMA-2026-04781RLUA-2026-05928

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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