Which versions of pyutiltool are malicious?

The following PyPI versions of pyutiltool are flagged malicious: 3.5. Treat any of these as compromised.

How do I remediate pyutiltool if I installed it?

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

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

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

Malicious package

pyutiltoolPyPI

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

MAL-2024-11686

Immediate action

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

pip uninstall pyutiltool

What this malware does

When importing the module and a specific file exists in the current directory, obfuscated code downloads and starts the next stage of obfuscated code (cstealer infostealer)

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

Campaign: 2024-10-pyutiltool

Reasons (based on the campaign):

infostealer
obfuscation
infostealer:cstealer

Malicious versions

1 flagged

3.5

Indicators of compromise (SHA-256)

3150e13656a8c745a109aaa2b3335a91344163c2b404eca84e00cafa84a69e6b

96c38386dcfd78ea5406622fc68853bcc4930be10f9b1b0f57af6035f51ec4cf

33b1b5a9f2482626b8ff1dc21fbf8da61082231e20f1b87060ab133957ce634f

3b212bc09ee1ae3ff6347f8b1413ba7d4d0192b110cfc6f4dc6a97b89b46c304

d79de5b129e8422486733bf10ecc2f118919fe140809bef940240914ab0f7cfa

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

Campaign

RLMA-2024-111432024-10-pyutiltoolRLUA-2026-00674

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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