Malicious Code Detected in bugbounty-test-123 Package - Version 99.1.0

bugbounty-test-123 Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1542: Malicious code in bugbounty-test-123 (npm). Affects bugbounty-test-123 versions 99.1.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'bugbounty-test-123' package is an npm library that is typically used for testing purposes in bug bounty programs. It allows developers to simulate various scenarios to identify vulnerabilities in their applications. However, version 99.1.0 of this package has been flagged for malicious behavior, specifically for communicating with a domain associated with malicious activity, which poses a significant risk to users.

Vulnerability Detail

The vulnerability in the 'bugbounty-test-123' package arises from its ability to communicate with a domain linked to malicious activities. This could lead to unauthorized data access, potential data breaches, or the execution of harmful code within the user's environment. The OpenSSF Package Analysis project identified this issue, emphasizing the importance of scrutinizing dependencies for hidden threats.

How To Fix

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

npm uninstall bugbounty-test-123

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, you may consider removing the 'bugbounty-test-123' package from your project until a secure version is released. You can do this by executing the following command: 'npm uninstall bugbounty-test-123'. This will prevent any malicious code execution while you await a fix.

Conclusion

The 'bugbounty-test-123' package version 99.1.0 has been identified as malicious due to its communication with a harmful domain. Users are advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for bugbounty-test-123 →

Share this vulnerability

FAQ

The package communicates with a domain known for malicious activities, which can lead to security breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Yes, you can temporarily uninstall the package or replace it with a safer alternative until a patched version is available.

It is crucial to remove the package immediately and monitor your application for any unusual behavior or security incidents.

Regularly check for updates and vulnerabilities in your dependencies, ideally as part of your continuous integration and deployment process.

How To Fix

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

npm uninstall bugbounty-test-123

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