Critical Malicious Code Vulnerability in company-billing-sdk-bugbounty Package

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1695: Malicious code in company-billing-sdk-bugbounty (npm). Affects company-billing-sdk-bugbounty 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 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 company-billing-sdk-bugbounty is an npm package designed to facilitate billing and payment processing for companies. It provides a set of APIs and tools that streamline the integration of billing functionalities into applications. However, this package has been identified to contain malicious code, posing significant risks to users who implement it in their projects.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the company-billing-sdk-bugbounty package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The specific version affected is 99.99.99, which has been flagged by security researchers for its harmful behavior.

How To Fix

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

npm uninstall company-billing-sdk-bugbounty

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 company-billing-sdk-bugbounty package from your project until a secure version is released. You can do this by executing the following command: npm uninstall company-billing-sdk-bugbounty.

Conclusion

The company-billing-sdk-bugbounty package has been identified with a critical vulnerability due to malicious code. Users are urged to update or uninstall the package to protect their applications from potential threats. Monitoring tools like Vulert can assist in real-time vulnerability detection.

See every vulnerability recorded for company-billing-sdk-bugbounty →

Share this vulnerability

FAQ

It is an npm package used for billing and payment processing in applications.

The malicious code can compromise application security, leading to unauthorized access and data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Yes, it is recommended to update the package to a secure version as soon as it is released.

As a temporary measure, you can uninstall the package to mitigate risks until a secure version is available.

How To Fix

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

npm uninstall company-billing-sdk-bugbounty

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