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

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?

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

Malicious package

pyinitePyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pyinite (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyinite across your stack and pipelines.
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 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.
How O3 protects you
O3 blocks pyinite 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. 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