Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@bmg-web/bmg-buttonnpm

Malicious code in @bmg-web/bmg-button (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2981
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @bmg-web/bmg-button

What this malware does

The package @bmg-web/bmg-button was found to contain malicious code.

The OpenSSF Package Analysis project identified '@bmg-web/bmg-button' @ 999.999.99 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
999.999.99

Indicators of compromise (SHA-256)

2458f054b53c52df146431a280cde6916e39f77fcc49e0bfaa2817b9a5f438e1
b59b2c3d1c98e7a5f4faae9549ed4f302c9273e1efeaee63e70f3013300327c2

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @bmg-web/bmg-button (version 999.999.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bmg-web/bmg-button across your stack and pipelines.

  2. If you installed it — respond

    Remove @bmg-web/bmg-button 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.

  3. Did it already run?

    If @bmg-web/bmg-button was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks @bmg-web/bmg-button before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @bmg-web/bmg-button on npm has been identified as a malicious package (version 999.999.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

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

@bmg-web/bmg-button (npm) malicious package — MAL-2026-2981 | O3 Security