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

bugbounty-test-123npm

Malicious code in bugbounty-test-123 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1542
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall bugbounty-test-123

What this malware does

The package bugbounty-test-123 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'bugbounty-test-123' @ 99.1.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
99.1.0

Indicators of compromise (SHA-256)

600a51644fc92800782199281268f1cd5cefb8fb611b9d82e9a169ea2aa3b477
c22630300fe50578818f50f4a068d400f9e434dc0341fff5a6cd0ca63e82d5e1

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 bugbounty-test-123 (version 99.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bugbounty-test-123 across your stack and pipelines.

  2. If you installed it — respond

    Remove bugbounty-test-123 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 bugbounty-test-123 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 bugbounty-test-123 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. bugbounty-test-123 on npm has been identified as a malicious package (version 99.1.0 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 bugbounty-test-123-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.

bugbounty-test-123 (npm) malicious package — MAL-2026-1542 | O3 Security