Which versions of pyiinstaller are malicious?

Every published version of pyiinstaller on PyPI is considered malicious. Remove the package entirely.

How do I remediate pyiinstaller if I installed it?

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

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

Search your lockfiles and build artifacts for pyiinstaller (all published versions).

Malicious package

pyiinstallerPyPI

pyiinstaller is a confirmed malicious PyPI package (MAL-2023-2068) that steals credentials and exfiltrates sensitive data. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyiinstaller (PyPI)

MAL-2023-2068

Immediate action

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

pip uninstall pyiinstaller

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)

4e820c2ce46a418e83b97aabee7b123b7f864e04b28fdb473d96fb2f7d629b91

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pyiinstaller (all published versions).
If you installed it — respond
pyiinstaller 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 pyiinstaller 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. pyiinstaller 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

medium.com

Credits

Checkmarx · finder

Detect & block this

O3 blocks pyiinstaller-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

Explore

All malware advisories How O3 detects malware Vulnerability database