Malicious Code Vulnerability in libxmljs13 Package

libxmljs13 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1773: Malicious code in libxmljs13 (npm). Affects libxmljs13 versions 0.30.1. 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

libxmljs13 is a JavaScript library that provides an interface for parsing and manipulating XML documents in Node.js applications. It is widely used for its ability to handle XML data efficiently and offers features such as XPath support and DOM manipulation. However, the package has been found to contain malicious code, which poses a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability in libxmljs13 stems from the presence of malicious code that can compromise the integrity of applications using this package. This code may allow attackers to execute arbitrary commands, leading to unauthorized access, data breaches, or system compromise. The malicious code was identified in version 0.30.1 of the package, and it is crucial for developers to be aware of this issue to protect their applications from potential exploitation.

How To Fix

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

npm uninstall libxmljs13

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

If immediate updating is not feasible, consider removing the libxmljs13 package from your project and replacing it with an alternative XML parsing library that does not have known vulnerabilities.

Conclusion

The discovery of malicious code in the libxmljs13 package highlights the importance of maintaining secure dependencies in software development. Developers should promptly update their packages and consider using tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for libxmljs13 →

Share this vulnerability

FAQ

The malicious code can execute arbitrary commands, potentially allowing attackers to gain unauthorized access to the system.

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

Consider removing the libxmljs13 package and using an alternative XML parsing library until you can safely update.

Version 0.30.1 of libxmljs13 contains the malicious code. It is advisable to update to the latest version or an alternative library.

Vulert uses your package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall libxmljs13

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