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

browser-gaming-clientnpm

Malicious code in browser-gaming-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1578
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall browser-gaming-client

What this malware does

The package browser-gaming-client was found to contain malicious code.

The OpenSSF Package Analysis project identified 'browser-gaming-client' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

4 flagged
99.0.099.0.399.0.499.0.5

Indicators of compromise (SHA-256)

7e9007604eefaa8b83b60ceee0ec3b2c45b2c0c666016fca81dc74eb94c21bcb
bef51d1e3b201fe1599636d4dbb8c131b18d6a53bda4f97eeee5cc34191413c4
d76349504f0aec6d7be105b14fafe74e673913f1ceb8652a8ef786cce58d0d22
499817d13773aa120b362da4545ff53901a8061328741dfce8dfd8ae9911360a
6192938bfd5be1cecf133866c6e290b57293bede88ca5b11d8af9aab40bae003

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 browser-gaming-client (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging browser-gaming-client across your stack and pipelines.

  2. If you installed it — respond

    Remove browser-gaming-client 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 browser-gaming-client 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 browser-gaming-client 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. browser-gaming-client on npm has been identified as a malicious package (versions 99.0.0, 99.0.3, 99.0.4, 99.0.5 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 browser-gaming-client-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.

browser-gaming-client (npm) malicious package — MAL-2026-1578 | O3 Security