Malicious Code Detected in carbon-invoice Package

carbon-invoice Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16544: Malicious code in carbon-invoice (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 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 carbon-invoice package is an npm library designed for generating invoices in a structured format. It is commonly used in web applications to facilitate billing processes. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the carbon-invoice package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical 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 carbon-invoice

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 carbon-invoice package from your project until a secure version is released. You can do this by executing: npm uninstall carbon-invoice. Alternatively, you may explore other invoice generation packages that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the carbon-invoice package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for carbon-invoice →

Share this vulnerability

FAQ

The carbon-invoice package is an npm library used for generating invoices in web applications.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

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.

Currently, there is no specific patched version available. Users are advised to update to the latest version or remove the package until a fix is released.

If immediate removal is not possible, ensure to monitor your application closely for any suspicious activities and consider implementing additional security measures.

How To Fix

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

npm uninstall carbon-invoice

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