Malicious Code Detected in libxmlussr Package - Security Alert

libxmlussr Updated 11 Dec 2025

Summary

11/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192463: Malicious code in libxmlussr (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

libxmlussr is an npm package designed for XML manipulation and processing. It provides developers with tools to handle XML data efficiently. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the libxmlussr package stems from the presence of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was identified by Amazon Inspector, highlighting the importance of monitoring open-source packages for security threats.

How To Fix

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

npm uninstall libxmlussr

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 may consider removing the libxmlussr package from your project until a secure version is available. You can do this by executing the following command: npm uninstall libxmlussr.

Conclusion

The discovery of malicious code in the libxmlussr package poses a serious threat to applications that utilize it. It is crucial for developers to update their dependencies and monitor their projects for vulnerabilities to maintain security. Utilizing tools like Vulert can aid in identifying and mitigating such risks effectively.

See every vulnerability recorded for libxmlussr →

Share this vulnerability

FAQ

libxmlussr is an npm package used for XML manipulation and processing in JavaScript applications.

The malicious code was detected by Amazon Inspector, a security tool that scans packages for vulnerabilities.

The risks include unauthorized access to sensitive data, potential data breaches, and the possibility of malicious actions being executed within the application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

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

How To Fix

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

npm uninstall libxmlussr

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