Which versions of crypto-pygame are malicious?

The following PyPI versions of crypto-pygame are flagged malicious: 10.14.7. Treat any of these as compromised.

How do I remediate crypto-pygame if I installed it?

Remove crypto-pygame from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed crypto-pygame — how do I know if it already compromised me?

If crypto-pygame 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.

How do I find crypto-pygame across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for crypto-pygame (version 10.14.7).

Malicious package

crypto-pygamePyPI

crypto-pygame is a confirmed malicious PyPI package (MAL-2023-1360) that executes malicious code on install (malicious version 10.14.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in crypto-pygame (PyPI)

MAL-2023-1360

Immediate action

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

pip uninstall crypto-pygame

What this malware does

The OpenSSF Package Analysis project identified 'crypto-pygame' @ 10.14.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

10.14.7

Indicators of compromise (SHA-256)

12204aa041b42e90b2749e8026e866fbe3d5ff07e79899073fbc585b9950b727

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for crypto-pygame (version 10.14.7).
If you installed it — respond
Remove crypto-pygame from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If crypto-pygame 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. crypto-pygame on PyPI has been identified as a malicious package (version 10.14.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks crypto-pygame-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database