Malicious Code Detected in libxmlfinal4 Package - Security Alert

libxmlfinal4 Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192453: Malicious code in libxmlfinal4 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libxmlfinal4 is an npm package designed for XML processing, providing functionalities that allow developers to manipulate XML data efficiently. However, it has been identified to contain malicious code, posing significant risks to applications that depend on it. This vulnerability can lead to unauthorized access or data manipulation, making it crucial for developers to address it promptly.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the libxmlfinal4 package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data or system integrity. The package was flagged by Amazon Inspector, indicating a serious security threat that could affect any application utilizing this package version.

How To Fix

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

npm uninstall libxmlfinal4

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 measure, you can remove the libxmlfinal4 package from your project until a secure version is available. You can do this by executing: npm uninstall libxmlfinal4. Alternatively, consider using a different XML processing library that does not have known vulnerabilities.

Conclusion

The discovery of malicious code in the libxmlfinal4 package poses a significant threat to applications relying on it. Developers are urged to take immediate action by updating or removing the package to safeguard their systems. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for libxmlfinal4 →

Share this vulnerability

FAQ

libxmlfinal4 is an npm package used for XML processing, allowing developers to manipulate and work with XML data in their applications.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

The malicious code can lead to unauthorized access, data manipulation, and potential compromise of sensitive information in applications using the package.

Yes, it is advisable to update to the latest version of libxmlfinal4 that addresses the malicious code issue. Use 'npm update libxmlfinal4' to update.

If immediate updates are not possible, consider removing the package or using an alternative library for XML processing 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 libxmlfinal4

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