Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

cyrptocomparePyPI

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

MAL-2023-1758
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall cyrptocompare

What this malware does

Attacker distributed 900+ malicious packages via PyPi, infecting local browsers with malicious extension to manipulate clipboard and replace crypto wallet addresses

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

e0b280ca1be335923a7f77b62cb936dcbbceedae2ede54fa60e9e5f255fb01c0

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cyrptocompare (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cyrptocompare across your stack and pipelines.

  2. If you installed it — respond

    cyrptocompare 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.

  3. Did it already run?

    If cyrptocompare 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.

  4. How O3 protects you

    O3 blocks cyrptocompare 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. cyrptocompare on PyPI has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Checkmarx · finder

Detect & block this

O3 blocks cyrptocompare-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

cyrptocompare (PyPI) malicious package — MAL-2023-1758 | O3 Security