Which versions of @spinstorm/eslint-config are malicious?

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

How do I remediate @spinstorm/eslint-config if I installed it?

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

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

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

Search your lockfiles and build artifacts for @spinstorm/eslint-config (version 99.99.99).

Malicious package

@spinstorm/eslint-confignpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7091

Immediate action

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

npm uninstall @spinstorm/eslint-config

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

078289291f72d4ca7e2f198dee6b538e35d40f7c187c61a51a03e2b7d7c80172

1da5df27759fd4c3da34935af44be933a3896247d22297d0811c333c853b3acb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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