Critical Malicious Code Vulnerability in bug-bounty Package

bug-bounty Updated 02 Oct 2025

Summary

17/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6914: Malicious code in bug-bounty (npm). Affects bug-bounty versions >= 1337.0.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 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 bug-bounty package is an npm library designed to facilitate bug bounty programs, allowing developers to manage vulnerabilities and rewards effectively. It provides tools for tracking submissions, communicating with researchers, and ensuring a streamlined process for vulnerability disclosure. However, this package has been found to communicate with a domain associated with malicious activity, raising significant security concerns for users and their applications.

Vulnerability Detail

The vulnerability stems from the bug-bounty package's communication with a domain linked to malicious activities. This connection can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The issue was introduced in version 1337.0.0, and it poses a risk to any application utilizing this version or later, as it may inadvertently expose sensitive information or allow for further attacks.

How To Fix

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

npm uninstall bug-bounty

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, consider removing the bug-bounty package from your project until a secure version is available. You can do this by running the following command: npm uninstall bug-bounty. Additionally, monitor your application for any unusual activity that may arise from the existing vulnerability.

Conclusion

The bug-bounty package has a critical vulnerability that allows communication with a malicious domain, posing serious security risks. Users are advised to update or remove the package to protect their applications. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.

See every vulnerability recorded for bug-bounty →

Share this vulnerability

FAQ

The bug-bounty package is an npm library that helps developers manage bug bounty programs, facilitating the tracking of vulnerabilities and rewards.

The vulnerability involves the package communicating with a malicious domain, which can lead to unauthorized access and potential data breaches.

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

If you are using version 1337.0.0 or later, immediately update the package to a secure version using 'npm update bug-bounty' or consider uninstalling it.

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

How To Fix

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

npm uninstall bug-bounty

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