NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

npm-bug-bounty-test1-rhyselsmorenpm

Advisory published Updated

npm-bug-bounty-test1-rhyselsmore is a confirmed malicious npm package (MAL-2026-6354) that executes malicious code on install (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in npm-bug-bounty-test1-rhyselsmore (npm)

MAL-2026-6354
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall npm-bug-bounty-test1-rhyselsmore

What this malware does

package.json declares a dependency foo whose source URL is https://3223567a82f3.ngrok.app/foo — an ephemeral, anonymous ngrok tunnel with no version pin and no integrity hash. On npm install, npm fetches whatever tarball the tunnel currently serves and runs its lifecycle scripts (preinstall/install/postinstall) on the installer's machine. The tunnel operator can swap the served bytes at any time, so the package effectively delegates arbitrary code execution at install time to whoever controls the ngrok endpoint. The package itself has no functional surface: the declared main: index.js is absent from the tarball (which contains only a foo text file and package.json), so the only observable effect of installing it is the dependency-resolution fetch from the attacker-controlled tunnel. Package naming suggests this may be a bug-bounty proof of concept, but the install-time mechanism is identical to a real dropper.

Malicious versions

1 flagged
1.0.5

Indicators of compromise (SHA-256)

354a2aa5da5356bab1c97537f865ebdf6af3fcc24f74a6f7c6f78181265c8af2

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for npm-bug-bounty-test1-rhyselsmore (version 1.0.5).

  2. If you installed it — respond

    Remove npm-bug-bounty-test1-rhyselsmore 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 npm-bug-bounty-test1-rhyselsmore 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. npm-bug-bounty-test1-rhyselsmore on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007388

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks npm-bug-bounty-test1-rhyselsmore-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.

Explore

npm-bug-bounty-test1-rhyselsmore (npm) malicious package — MAL-2026-6354 | O3 Security