Malicious Code Detected in libxmljs2qwerty: npm Package Vulnerability

libxmljs2qwerty Updated 09 Dec 2025

Summary

09/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192389: Malicious code in libxmljs2qwerty (npm). Affects libxmljs2qwerty versions 0.30.30. 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

libxmljs2qwerty is a JavaScript library designed for XML parsing and manipulation, commonly used in Node.js applications. It provides developers with a simple API to work with XML data structures. However, the version 0.30.30 of this package has been identified as malicious, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in libxmljs2qwerty arises from its malicious behavior, which includes communication with a domain linked to harmful activities and the execution of commands that can compromise system integrity. This can lead to unauthorized access, data breaches, or further exploitation of the affected system.

How To Fix

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

npm uninstall libxmljs2qwerty

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 avoid using the libxmljs2qwerty package altogether until a secure version is confirmed. Review your project's dependencies and consider replacing it with a trusted XML parsing library.

Conclusion

The discovery of malicious code in the libxmljs2qwerty package highlights the importance of vigilance in managing open-source dependencies. By promptly addressing this vulnerability through updates and monitoring tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for libxmljs2qwerty →

Share this vulnerability

FAQ

libxmljs2qwerty is a JavaScript library for parsing and manipulating XML data in Node.js applications.

You can check if your application is affected by using Vulert, which monitors vulnerabilities in open-source packages. Visit Vulert Scanner to analyze your package-lock.json file.

Using the malicious version can lead to unauthorized access, data breaches, and potential exploitation of your system by attackers.

There is no patch for the malicious version 0.30.30. The recommended action is to uninstall this version and install a secure alternative.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to the packages you use.

How To Fix

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

npm uninstall libxmljs2qwerty

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