Which versions of uitil are malicious?

The following PyPI versions of uitil are flagged malicious: 0.1.4, 0.1.5. Treat any of these as compromised.

How do I remediate uitil if I installed it?

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

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

Yes — uitil is associated with the 2026-01-uitil 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 uitil 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 uitil (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uitil across your stack and pipelines.

Malicious package

uitilPyPI

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

MAL-2026-1036

Immediate action

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

pip uninstall uitil

What this malware does

The package implements an undocumented way to execute code hidden in image files, and a function that searches for images in the current directory and attempts to execute the code.

It's used in the GitHub repository https://github.com/OR-6/PassCheck/blob/main/main.py#L190 to silently execute the command hidden in the image https://github.com/OR-6/PassCheck/blob/b09b3f1ec5d7345c614b1d956840ee2774f7131b/demo.png when the user interacts with the repository code. The decrypted command attempted to download and execute code from hxxps://or-6.github[.]io, which at the time of analysis didn't host any code.

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

Campaign: 2026-01-uitil

Reasons (based on the campaign):

typosquatting
steganography
The malicious code is intentionally included in a dependency of the package
action-hidden-in-lib-usage
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

2 flagged

0.1.40.1.5

Indicators of compromise (SHA-256)

ff0b75197d8e7cd361d61461260811fba8920c54b8538cb5f21ec2fc1c885ec3

243b442528547767d2f56c9ced8cb1b6791997d176602ecc4725194f684fdb05

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

Campaign

2026-01-uitil

References

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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