Malicious Code Vulnerability in libxmlfinal3 Package

libxmlfinal3 Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192452: Malicious code in libxmlfinal3 (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

libxmlfinal3 is an npm package designed for XML parsing and manipulation. It provides developers with tools to handle XML data efficiently. However, the package has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities within affected systems.

Vulnerability Detail

The vulnerability in libxmlfinal3 originates from the presence of malicious code embedded within the package. This code can execute harmful operations without the user's consent, potentially compromising the integrity and confidentiality of the application. The malicious nature of this vulnerability allows attackers to exploit it for various malicious purposes, including data theft and unauthorized system access.

How To Fix

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

npm uninstall libxmlfinal3

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 may consider removing the libxmlfinal3 package from your project until a secure version is available. You can do this by executing the command: npm uninstall libxmlfinal3. This will prevent any potential exploitation of the malicious code while you seek a safer alternative.

Conclusion

The libxmlfinal3 package has been found to contain malicious code, posing serious security risks to applications that utilize it. It is crucial to update the package to a secure version or remove it from your project to mitigate potential threats. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for libxmlfinal3 →

Share this vulnerability

FAQ

libxmlfinal3 is an npm package used for XML parsing and manipulation in JavaScript applications.

The malicious code can execute unauthorized operations, potentially leading to data breaches and system compromises.

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

Consider uninstalling the libxmlfinal3 package as a temporary measure until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall libxmlfinal3

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