Which versions of pygame-install are malicious?

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

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

Remove pygame-install 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 pygame-install — how do I know if it already compromised me?

If pygame-install 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 pygame-install across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pygame-install (version 17.14.20).

Malicious package

pygame-installPyPI

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

Malicious code in pygame-install (PyPI)

MAL-2023-1389

Immediate action

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

pip uninstall pygame-install

What this malware does

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

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

17.14.20

Indicators of compromise (SHA-256)

93390eea0977ef15ff0c7413e64df5bd99497ea76e9238097ee0b6f4b9862fdd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pygame-install (version 17.14.20).
If you installed it — respond
Remove pygame-install 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 pygame-install 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. pygame-install on PyPI has been identified as a malicious package (version 17.14.20 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 pygame-install-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