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

@bmg-web/bmg-cardnpm

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

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

What this malware does

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

The OpenSSF Package Analysis project identified '@bmg-web/bmg-card' @ 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)

59b3c5f9a33fdf7b85e1454292063fa2b999025b485c1dc76d09c6c655de6bba
e6b0a1542df5f356749bb120307f24588161f99389b5630aade5a178b2ac98c6

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-card (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-card across your stack and pipelines.

  2. If you installed it — respond

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