Which versions of xsltproc are malicious?

The following PyPI versions of xsltproc are flagged malicious: 0.0.0, 0.0.1. Treat any of these as compromised.

How do I remediate xsltproc if I installed it?

xsltproc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed xsltproc — how do I know if it already compromised me?

If xsltproc was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is xsltproc part of a known attack campaign?

Yes — xsltproc is associated with the GENERIC-standard-pypi-install-pentest, RLMA-2025-06599, RLUA-2026-00938 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find xsltproc across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xsltproc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xsltproc across your stack and pipelines.

Malicious package

xsltprocPyPI

Malicious code in xsltproc (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191937

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall xsltproc

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.00.0.1

Indicators of compromise (SHA-256)

94b6ec5a0fb20f1b9fa39f68bf162310cba022382218c6e1bd780b9d20df6492

9038d06e907a027d385f7ef9111815ca61e7b26fce85196a549c20e02447adc4

5e115c4d9e37a74425bbfeb354346eed891480d56449f622b55365587a6fad5e

9e2645a5079046dd2c4cac20f820bcc2ff680dec5e0d4d8d122e3aaf20218cf1

ad9780b20cabbcb8decdfe592cfc4a5d843e325fdcebcfc83d6cf22b82241f1b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for xsltproc (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging xsltproc across your stack and pipelines.
If you installed it — respond
xsltproc is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If xsltproc was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks xsltproc before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. xsltproc on PyPI has been identified as a malicious package (versions 0.0.0, 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestRLMA-2025-06599RLUA-2026-00938

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks xsltproc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring