Which versions of pyiniter are malicious?

The following PyPI versions of pyiniter are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate pyiniter if I installed it?

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

If pyiniter 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 pyiniter part of a known attack campaign?

Yes — pyiniter is associated with the RLMA-2025-02588, 2025-05-pyiniter, RLUA-2026-00636 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 pyiniter 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 pyiniter (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyiniter across your stack and pipelines.

Malicious package

pyiniterPyPI

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

MAL-2025-4231

Immediate action

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

pip uninstall pyiniter

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

1 flagged

0.1.0

Indicators of compromise (SHA-256)

8ddb7a7d0116fa67908d4496e52654e39ac6cc0f187df4dfd8a57b0ae9f092dd

aae1c71f553a591485f1f936a908bacbb5443253e92364e1092163d80a40333b

9f926429e9f976b0e3fe7deca152e047fef9ff22705a9e59cf492dab0397389d

76141c8b8089db40c02d9c86db17572414dcaf7d02c1a5872245e3a9a15c7d92

f104c7e7387c2f00fd71cedc0d1e78494e85c877cebf319362be7ac58dd84c57

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 pyiniter (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyiniter across your stack and pipelines.
If you installed it — respond
pyiniter 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 pyiniter 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 pyiniter 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. pyiniter on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025882025-05-pyiniterRLUA-2026-00636

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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