Which versions of pyinite are malicious?

The following PyPI versions of pyinite are flagged malicious: 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8, 0.1.9. Treat any of these as compromised.

How do I remediate pyinite if I installed it?

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

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

Is pyinite part of a known attack campaign?

Yes — pyinite is associated with the 2025-05-pyiniter 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 pyinite across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pyinite (6 malicious versions).

Malicious package

pyinitePyPI

Advisory published May 9, 2025Updated Dec 12, 2025

pyinite is a confirmed malicious PyPI package (MAL-2025-191834) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.4, 0.1.5, 0.1.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyinite (PyPI)

MAL-2025-191834

Immediate action

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

pip uninstall pyinite

What this malware does

File is designed to download, hide under system-like name, and run a remote executable, widely identified as malicious.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-05-pyiniter

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

6 flagged

0.1.40.1.50.1.60.1.70.1.80.1.9

Indicators of compromise (SHA-256)

a8af051de51bb2f1de27a6efc1c2eceb6176a1df26e1cddf6de17312a90e9cf8

7ed8f43159750189f4cea17185b5ee087dda83db8574bf258010068c524fc723

2cd19720780eef05ac60ba717973c42bc1761c875e091e93d1ccab65b37527ff

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pyinite (6 malicious versions).
If you installed it — respond
pyinite 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 pyinite 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. pyinite 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, 0.1.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-05-pyiniter

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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