Critical Malicious Code Vulnerability in test-bugbounty-package-6

test-bugbounty-package-6 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1862: Malicious code in test-bugbounty-package-6 (npm). Affects test-bugbounty-package-6 versions 99.99.99. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The test-bugbounty-package-6 is an npm package designed for testing purposes in bug bounty programs. It provides various functionalities to simulate vulnerabilities and assess security measures. However, this package has been compromised, leading to the introduction of malicious code that can potentially harm users and their systems.

Vulnerability Detail

The vulnerability in test-bugbounty-package-6 arises from the inclusion of malicious code that can execute harmful actions on the user's system. This code was identified in version 99.99.99 of the package and poses significant risks, including unauthorized access to sensitive data, system compromise, and potential exploitation by attackers. The origin of this vulnerability is linked to malicious actors who have manipulated the package to serve their interests, making it crucial for users to take immediate action.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall test-bugbounty-package-6

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can remove the test-bugbounty-package-6 from their project until a secure version is available. This can be done using the following command: npm uninstall test-bugbounty-package-6.

Conclusion

The test-bugbounty-package-6 has been identified with a critical vulnerability due to the presence of malicious code. Users are urged to take immediate action by updating or removing the package to safeguard their systems. Continuous monitoring and prompt updates are essential to maintain security in software development.

See every vulnerability recorded for test-bugbounty-package-6 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that can execute harmful actions on the user's system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

You should immediately update the package to a patched version once it is available or remove it from your project.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

Detailed information can be found on the GitHub repository of the malicious packages or through security advisories related to npm packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall test-bugbounty-package-6

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback