Which versions of pxz are malicious?

The following PyPI versions of pxz are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, 1.1.9, 1.1.10, 1.1.11, 1.1.12, 1.1.13, 1.1.14. Treat any of these as compromised.

How do I remediate pxz if I installed it?

pxz 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 pxz — how do I know if it already compromised me?

If pxz 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 pxz part of a known attack campaign?

Yes — pxz is associated with the RLMA-2025-01229, RLUA-2025-01986, 2025-02-pxz, RLUA-2026-00617 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 pxz 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 pxz (14 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pxz across your stack and pipelines.

Malicious package

pxzPyPI

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

MAL-2025-1986

Immediate action

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

pip uninstall pxz

What this malware does

Packages are designed to collect basic info about the user when importing them, and have no other purpose. While they claim to do so, some packages from the same uploader use confusing names, clearly suggesting the intention to harvest data from unintentional installations.

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: 2025-02-pxz

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.
typosquatting

Malicious versions

14 flagged

1.1.11.1.21.1.31.1.41.1.51.1.61.1.71.1.81.1.91.1.101.1.111.1.121.1.131.1.14

Indicators of compromise (SHA-256)

b25b6647f8eca0732c744fd3d3c1f01bfd645272a1990e4568c6c3e4c04ef197

e6820944501214f52abd2d29fa703d5f9dee7ca307303cc50898af9333372451

050a6afc1a06be5f177dac6d46cb0ac3248ee389ab04e5d0f0deb7f0bfc72e5f

2649e06884047fa82f596d9f9b0822080bff93b64a69a9a6090c0640f19ec656

9b0987e1f97aba7fa174dd59023b4391aceb42d3ddd34f742d168db0be47d832

b425ca89874601489e94945fa9f292364fb3887ba83f1999da05dc4ca1c2670a

b0f3a4731c9c4fe85a738cb059a02a214ab5c81d3a5b9cd094828401e6113046

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 pxz (14 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pxz across your stack and pipelines.
If you installed it — respond
pxz 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 pxz 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 pxz 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. pxz on PyPI has been identified as a malicious package (versions 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, 1.1.6, 1.1.7, 1.1.8, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01229RLUA-2025-019862025-02-pxzRLUA-2026-00617

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks pxz-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