Malicious Code Detected in facturae Package - Security Alert

facturae Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20152: Malicious code in facturae (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 facturae package is an npm library designed for generating electronic invoices in compliance with Spanish regulations. It is widely used in applications that require invoicing functionalities. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the facturae package, which was introduced in version 0 and affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. Users of the package are at risk of having their sensitive information compromised, making it crucial to address this issue promptly.

How To Fix

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

npm uninstall facturae

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 using an alternative package for invoicing or implementing custom code to handle invoicing functionalities until the facturae package is secured. For example, you can create a simple invoicing function in your application without relying on external libraries.

Conclusion

The facturae package has been identified as containing malicious code, which poses a serious threat to users. It is crucial to take immediate action by uninstalling the affected package and updating to a secure version or using alternative solutions. Regular monitoring of dependencies using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for facturae →

Share this vulnerability

FAQ

The facturae package is an npm library used for generating electronic invoices in compliance with Spanish regulations.

The malicious code can lead to unauthorized access and data breaches, posing significant security risks to users.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

You should uninstall the affected version of facturae and update to a patched version or consider using an alternative package for invoicing.

While waiting for a fix, consider using alternative invoicing solutions or custom implementations to avoid exposure to the vulnerability.

How To Fix

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

npm uninstall facturae

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