Which versions of ccxt-mexc-futures are malicious?

The following PyPI versions of ccxt-mexc-futures are flagged malicious: 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8. Treat any of these as compromised.

How do I remediate ccxt-mexc-futures if I installed it?

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.

I already installed ccxt-mexc-futures — how do I know if it already compromised me?

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

Yes — ccxt-mexc-futures is associated with the RLMA-2025-02500, RLUA-2025-02560, 2025-03-ccxt-mexc-futures, RLUA-2026-00181 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-mexc-futures 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 ccxt-mexc-futures (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ccxt-mexc-futures across your stack and pipelines.

Malicious package

ccxt-mexc-futuresPyPI

Malicious code in ccxt-mexc-futures (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3439

Immediate action

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

pip uninstall ccxt-mexc-futures

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

5 flagged

0.1.40.1.50.1.60.1.70.1.8

Indicators of compromise (SHA-256)

f8948ced2172fde60eaa2844530b5eb6d7f7e1c3e46860ffe1787d069de422d5

b960a73138bba5d79c9eaf82de51d667fc6305ab577d2bea22bde2b3535461bc

116fc2e7a8fe6b235f43036def48255cb8c8a75e7ad046f94155903e29403ca2

f2eb5eb75679b536c430ad6d5440e63fbe1d1cd391ab1abf2a411dae3a768ed8

f126fba8fb0e9d3ab356f93681fa35fcec759a2c6af2c6ab549e344ccfe85d38

ab711c6084603ee25b3619cb1e58fc0581b22e3a8ce3c15d13fa86252b12eafc

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 ccxt-mexc-futures (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ccxt-mexc-futures across your stack and pipelines.
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 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 ccxt-mexc-futures 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. ccxt-mexc-futures on PyPI has been identified as a malicious package (versions 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02500RLUA-2025-025602025-03-ccxt-mexc-futuresRLUA-2026-00181

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.

Malware detection Runtime egress monitoring