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

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

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

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

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

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

Search your lockfiles and build artifacts for @bmg-web/bmg-multiselect (2 malicious versions).

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

Malicious package

@bmg-web/bmg-multiselectnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

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

MAL-2026-7052

Immediate action

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

npm uninstall @bmg-web/bmg-multiselect

Malicious versions

2 flagged

999.9.9999.9999.99

Indicators of compromise (SHA-256)

39e305caaa5261e5dbccd8ec174a5b3dde2a4d518f0c7ac1d1f885098f45b003

a39d0c01e412bb0eb3187095eccc99dec6767c82469fdafbc7991d6ea71d5e50

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04686RLUA-2026-05827

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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