Which versions of pyinitialyze are malicious?

The following PyPI versions of pyinitialyze are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate pyinitialyze if I installed it?

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

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

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

Malicious package

pyinitialyzePyPI

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

MAL-2025-4232

Immediate action

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

pip uninstall pyinitialyze

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

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

90d7519f9156ff149d0fa94da1e85d50c27a9a0bbcf946f2263ac6d25917efa2

1621d6c55a74c36518d747769d09d6d528e25e7f4e2b634dce25ba051f9710a0

17fb73bd9014366b80018d085cf68a67535ca979bd2ddd14c82ef27ec1309a61

c1adbe26b4a61a20ca23151d41cba3d3b3d9ccb5b3326f1a83338c186f01fa79

fb0b479e81e25c9facc45612554f1b56627b7cc45600f15858e97111b29ca2ff

996fb96ad0af494f7650b47003f014cc1e71b7d0c2fb3271964e1ba33e8fa1d5

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

Campaign

RLMA-2025-025892025-05-pyiniterRLUA-2026-00637RLUA-2026-02076

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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