Malicious Code Vulnerability in libxmljs10 Package

libxmljs10 Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192456: Malicious code in libxmljs10 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

libxmljs10 is a JavaScript library that provides an interface for parsing and manipulating XML documents. It is commonly used in Node.js applications for handling XML data. The package is known for its efficiency and ease of use, but it has recently been identified as containing malicious code that poses significant security risks to applications that rely on it.

Vulnerability Detail

The vulnerability in libxmljs10 stems from the presence of malicious code that can compromise the integrity of applications using this package. This issue was reported by Amazon Inspector, which identified the package as containing harmful elements that could lead to unauthorized access, data breaches, or other malicious activities. The vulnerability affects all versions of the package, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall libxmljs10

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 libxmljs10 package from your project until a secure version is released. You can do this by running the command: npm uninstall libxmljs10. This will prevent the malicious code from executing in your application.

Conclusion

The libxmljs10 package has been identified as containing malicious code, posing a significant security risk to applications that utilize it. Users are strongly advised to update or remove the package to mitigate potential threats. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for libxmljs10 →

Share this vulnerability

FAQ

libxmljs10 is a JavaScript library used for parsing and manipulating XML documents in Node.js applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize this package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If an immediate update is not possible, consider removing the libxmljs10 package from your project as a temporary measure.

The vulnerability was reported 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 libxmljs10

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