Malicious Code Vulnerability in libxmljsololoq Package

libxmljsololoq Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1787: Malicious code in libxmljsololoq (npm). Affects libxmljsololoq versions 0.30.4. 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

libxmljsololoq is an npm package that provides XML parsing capabilities for JavaScript applications. It is designed to facilitate the manipulation and processing of XML data structures. However, this package has been identified as containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the libxmljsololoq package. This code can potentially compromise the integrity of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The specific version affected is 0.30.4, which was reported by ReversingLabs. The malicious behavior can be triggered when the package is executed, allowing attackers to exploit the vulnerability for nefarious purposes.

How To Fix

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

npm uninstall libxmljsololoq

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 can remove the libxmljsololoq package from your project if it is not critical to your application. You can do this by running the command: npm uninstall libxmljsololoq. This will prevent any potential exploitation until a secure version is available.

Conclusion

The libxmljsololoq package has been identified as containing malicious code, which poses a significant risk to applications using it. It is crucial to update or remove the package to mitigate potential security threats. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for libxmljsololoq →

Share this vulnerability

FAQ

libxmljsololoq is an npm package used for XML parsing in JavaScript applications.

The malicious code can compromise application integrity, leading to unauthorized access and potential data breaches.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Consider removing the libxmljsololoq package from your project as a temporary measure until a secure version is available.

The vulnerability was reported by ReversingLabs, a security research firm.

How To Fix

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

npm uninstall libxmljsololoq

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