Which versions of ccxt-telemetry are malicious?

The following PyPI versions of ccxt-telemetry are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate ccxt-telemetry if I installed it?

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

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

Yes — ccxt-telemetry is associated with the 2026-04-ccxt-telemetry 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 ccxt-telemetry across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ccxt-telemetry (version 1.0.5).

Malicious package

ccxt-telemetryPyPI

Advisory published Apr 15, 2026Updated Apr 15, 2026

ccxt-telemetry is a confirmed malicious PyPI package (MAL-2026-2697) that steals credentials and exfiltrates sensitive data (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ccxt-telemetry (PyPI)

MAL-2026-2697

Immediate action

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

pip uninstall ccxt-telemetry

What this malware does

During installation, code exfiltrates environment variables and sensitive keys from .env files

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

Campaign: 2026-04-ccxt-telemetry

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.
exfiltration-env-variables
exfiltration-credentials

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

c3e38f4b70af5228dbb3bc058a3a413daa01d50884e42e8e70b68454163118ba

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for ccxt-telemetry (version 1.0.5).
If you installed it — respond
ccxt-telemetry 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 ccxt-telemetry 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. ccxt-telemetry on PyPI has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-ccxt-telemetry

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks ccxt-telemetry-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