Which versions of venomenallib are malicious?

The following PyPI versions of venomenallib are flagged malicious: 0.1.1, 0.1.2, 0.1.3, 2.7.0. Treat any of these as compromised.

How do I remediate venomenallib if I installed it?

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

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

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

Malicious package

venomenallibPyPI

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

MAL-2025-191920

Immediate action

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

pip uninstall venomenallib

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

4 flagged

0.1.10.1.20.1.32.7.0

Indicators of compromise (SHA-256)

2a387baa817f41f73fc124cce2b5071b4d11aee780c5baf31d5707d301425304

4f33bd81b0b06fd056a05286d3664de55bbaff5fa8c1a54a07905e8e3b5e596a

2adc0f4bca29170dd75bba6b0f6888b18ed233d54b407dcfd9b3a28b0e5ab592

5367869075162c2cb355d06c6249467735fcc7b6e081279497172d94c97b1016

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

Campaign

2025-08-xenlib

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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