Which versions of py-clob-clients are malicious?

The following PyPI versions of py-clob-clients are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.4, 0.1.5, 0.1.7, 0.1.8. Treat any of these as compromised.

How do I remediate py-clob-clients if I installed it?

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

If py-clob-clients was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is py-clob-clients part of a known attack campaign?

Yes — py-clob-clients is associated with the 2026-05-py-clob-clients 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 py-clob-clients across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for py-clob-clients (7 malicious versions).

Malicious package

py-clob-clientsPyPI

Advisory published May 1, 2026Updated May 1, 2026

py-clob-clients is a confirmed malicious PyPI package (MAL-2026-3220) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in py-clob-clients (PyPI)

MAL-2026-3220

Immediate action

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

pip uninstall py-clob-clients

What this malware does

Package exfiltrates env variables from .env files. It's a typosquatting of a legitimate package and is used in a malicious GitHub repository

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

Campaign: 2026-05-py-clob-clients

Reasons (based on the campaign):

typosquatting
crypto-related
exfiltration-env-variables
action-hidden-in-lib-usage
The malicious code is intentionally included in a dependency of the package

Malicious versions

7 flagged

0.1.00.1.10.1.20.1.40.1.50.1.70.1.8

Indicators of compromise (SHA-256)

7136140b365c314a42f5efe300779f093c40a41fb5c2258c7f5ff05c88eba2f8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for py-clob-clients (7 malicious versions).
If you installed it — respond
py-clob-clients 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 py-clob-clients was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. py-clob-clients on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.4, 0.1.5, 0.1.7, 0.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-py-clob-clients

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks py-clob-clients-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

Explore

All malware advisories How O3 detects malware Vulnerability database