ccxt-mexc-futuresPyPI
Advisory published Updated
ccxt-mexc-futures is a confirmed malicious PyPI package (MAL-2025-3439) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.4, 0.1.5, 0.1.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ccxt-mexc-futures (PyPI)
What this malware does
There is a hidden code that overwrites the default method and downloads remote data, which contains the dictionary pretending to be the right value, and a hidden code to exfiltrate machine ID and download and run a remote code.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2025-03-ccxt-mexc-futures
Reasons (based on the campaign):
-
obfuscation
-
Downloads and executes a remote malicious script.
-
action-hidden-in-lib-usage
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for ccxt-mexc-futures (5 malicious versions).
If you installed it — respond
ccxt-mexc-futures 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-mexc-futures 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
Campaign
References
Credits
- Kamil Mańkowski (kam193)
- ReversingLabs · finder
Detect & block this
O3 blocks ccxt-mexc-futures-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.