Which versions of @bmg-web/bmg-spinner are malicious?

The following npm versions of @bmg-web/bmg-spinner are flagged malicious: 999.9999.99. Treat any of these as compromised.

How do I remediate @bmg-web/bmg-spinner if I installed it?

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

If @bmg-web/bmg-spinner 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 @bmg-web/bmg-spinner part of a known attack campaign?

Yes — @bmg-web/bmg-spinner is associated with the RLMA-2026-04689, RLUA-2026-05830 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 @bmg-web/bmg-spinner across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bmg-web/bmg-spinner (version 999.9999.99).

Part of a larger attack: @bmg-web published 16 malicious packages. See the full campaign →

Malicious package

@bmg-web/bmg-spinnernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@bmg-web/bmg-spinner is a confirmed malicious npm package (MAL-2026-7055) that executes malicious code on install (malicious version 999.9999.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bmg-web/bmg-spinner (npm)

MAL-2026-7055

Immediate action

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

npm uninstall @bmg-web/bmg-spinner

Malicious versions

1 flagged

999.9999.99

Indicators of compromise (SHA-256)

9f4f2b352dbdf3f8bdce56400bd17554da43f0c09ed502c8d773e50b339a0079

97246c98b71118af412678eb36ea79ab976da67619ccde22861d18d0d4b9c800

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04689RLUA-2026-05830

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @bmg-web/bmg-spinner-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