Which versions of test-bugbounty-package-6 are malicious?

The following npm versions of test-bugbounty-package-6 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate test-bugbounty-package-6 if I installed it?

Remove test-bugbounty-package-6 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.

I already installed test-bugbounty-package-6 — how do I know if it already compromised me?

If test-bugbounty-package-6 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.

Is test-bugbounty-package-6 part of a known attack campaign?

Yes — test-bugbounty-package-6 is associated with the RLMA-2026-01613 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find test-bugbounty-package-6 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for test-bugbounty-package-6 (version 99.99.99).

Malicious package

test-bugbounty-package-6npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

test-bugbounty-package-6 is a confirmed malicious npm package (MAL-2026-1862) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-bugbounty-package-6 (npm)

MAL-2026-1862

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall test-bugbounty-package-6

What this malware does

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

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

fedd33b0155569ba11754cf52efd937fb6200647cddf2eb1aa2e8ae39b0b1fb8

52ee2c6095d9dfd6bdd4945e804a736035b9e29d4265e6a0e455aff026911be7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for test-bugbounty-package-6 (version 99.99.99).
If you installed it — respond
Remove test-bugbounty-package-6 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.
Did it already run?
If test-bugbounty-package-6 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. test-bugbounty-package-6 on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01613

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks test-bugbounty-package-6-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

Explore

All malware advisories How O3 detects malware Vulnerability database