Malicious Code Exfiltration in xsltproc Package

xsltproc Updated 03 Dec 2025

Summary

14/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191937: Malicious code in xsltproc (PyPI). Affects xsltproc versions 0.0.0 – 0.0.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The xsltproc package, available on PyPI, is designed for processing XML files using XSLT stylesheets. It is commonly used in various applications for transforming XML data into different formats. However, this package has been identified as containing malicious code that compromises user data.

Vulnerability Detail

The vulnerability originates from the package's code, which is designed to exfiltrate basic information about the host system, such as the IP address and username, upon installation or import. This malicious behavior is executed by overriding the install command in the setup.py file, leading to unauthorized data access without the user's consent. The package poses a limited risk but can still lead to privacy breaches.

How To Fix

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

pip uninstall xsltproc

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 workaround, you can avoid using the xsltproc package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your environment for any unauthorized data access.

Conclusion

The xsltproc package has been identified as containing malicious code that exfiltrates sensitive information from the host system. Users are advised to uninstall the package and consider alternatives to safeguard their data. Regular monitoring for vulnerabilities is crucial to maintaining a secure environment.

See every vulnerability recorded for xsltproc →

Share this vulnerability

FAQ

xsltproc is a package used for processing XML files with XSLT stylesheets, commonly utilized in data transformation tasks.

The vulnerability allows the package to exfiltrate sensitive information from your system, potentially compromising your privacy.

You should uninstall the xsltproc package immediately to prevent any unauthorized data access.

Yes, consider using other XML processing libraries that do not have known vulnerabilities.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your Pipfile.lock. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

pip uninstall xsltproc

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