Which versions of zenomenallib are malicious?

The following PyPI versions of zenomenallib are flagged malicious: 2.7.0. Treat any of these as compromised.

How do I remediate zenomenallib if I installed it?

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

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

Yes — zenomenallib is associated with the RLMA-2025-04824, 2025-08-xenlib, RLUA-2026-00947 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 zenomenallib 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 zenomenallib (version 2.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zenomenallib across your stack and pipelines.

Malicious package

zenomenallibPyPI

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

MAL-2025-47814

Immediate action

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

pip uninstall zenomenallib

What this malware does

Package is prepared to exfiltrate sensitive files. Different packages use different places for the malicious code: it runs during importing the module, is placed in a native binary, or in the setup.py script

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-xenlib

Reasons (based on the campaign):

files-exfiltration

Malicious versions

1 flagged

2.7.0

Indicators of compromise (SHA-256)

aaf7926d44586ea02f00b2336539321cd4a1e5b42598161df6f1209baa693bf7

3324eaf85f9368bc891dd089cd413ce957702dabc36c0dfc0c1280c384e3bc56

4c6be0b94e3c9643885ae8893cd9523bd5ad735965a16a3df64a347bd38f8016

a684f623b574b542e54511cf3c3530dc551825eed72db6de1b1ea5584cb571e8

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 zenomenallib (version 2.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zenomenallib across your stack and pipelines.
If you installed it — respond
zenomenallib 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 zenomenallib 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 zenomenallib 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. zenomenallib on PyPI has been identified as a malicious package (version 2.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-048242025-08-xenlibRLUA-2026-00947

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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