Malicious Code Detected in libxmlfinal Package - Security Alert

libxmlfinal Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192451: Malicious code in libxmlfinal (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

libxmlfinal is an npm package designed for XML processing, providing utilities for parsing and manipulating XML data. It is commonly used in various Node.js applications for handling XML files. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in libxmlfinal originates from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that depend on libxmlfinal, leading to unauthorized access, data breaches, or other malicious activities. The malicious nature of this code was identified by Amazon Inspector, which flagged the package for containing harmful elements that could exploit vulnerabilities in the host application.

How To Fix

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

npm uninstall libxmlfinal

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 libxmlfinal package from your project if it is not critical to your application's functionality. You can do this by running the following command: npm uninstall libxmlfinal. Consider using alternative libraries that provide similar functionality without the security risks.

Conclusion

The discovery of malicious code in the libxmlfinal package highlights the importance of regularly monitoring and updating dependencies in software projects. By following the recommended steps to fix the vulnerability and utilizing tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for libxmlfinal →

Share this vulnerability

FAQ

libxmlfinal is an npm package used for XML processing in Node.js applications.

The malicious code was identified by Amazon Inspector, which scans packages for security vulnerabilities.

Using libxmlfinal can expose your application to security threats, including unauthorized access and data breaches.

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 or using alternative libraries 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 libxmlfinal

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