Critical Malicious Code Vulnerability in funbill Package

funbill Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21044: Malicious code in funbill (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The funbill package is an npm library designed to facilitate billing and payment processing in web applications. It offers features such as invoice generation, payment tracking, and integration with various payment gateways. However, the package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the funbill package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access to sensitive data, manipulation of application behavior, or even complete takeover of the affected application. The malicious nature of this vulnerability makes it critical for developers to address it immediately to prevent potential exploitation.

How To Fix

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

npm uninstall funbill

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 can remove the funbill package from your project until a secure version is released. You can do this by executing the following command: npm uninstall funbill. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The funbill package has been found to contain malicious code, posing serious security risks to applications that utilize it. Developers are urged to update or remove the package immediately to mitigate potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for funbill →

Share this vulnerability

FAQ

The funbill package is an npm library used for billing and payment processing in web applications.

The malicious code can lead to unauthorized access and manipulation of sensitive data within applications.

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

If immediate updates are not possible, consider removing the package and using alternative solutions until a secure version is available.

Utilize tools like Vulert, which can monitor your package-lock.json file for vulnerabilities and provide real-time alerts.

How To Fix

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

npm uninstall funbill

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