Which versions of noonutil are malicious?

The following PyPI versions of noonutil are flagged malicious: 0.1, 0.1.0, 0.1.1, 0.2, 0.3, 0.4. Treat any of these as compromised.

How do I remediate noonutil if I installed it?

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

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

Yes — noonutil is associated with the RLMA-2025-04793, GENERIC-standard-pypi-install-pentest, RLUA-2026-00560 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 noonutil 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 noonutil (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging noonutil across your stack and pipelines.

Malicious package

noonutilPyPI

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

MAL-2025-47788

Immediate action

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

pip uninstall noonutil

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

6 flagged

0.10.1.00.1.10.20.30.4

Indicators of compromise (SHA-256)

d1a93e361635e2daadbe7c56e33275a86b68cb7422746c452ca67c05fc134585

3a4bb942985d4d53f8b74d2a53a67b036f66a9097878952785a8b9f33b5485b2

98fa038a694e6d6093bffd74d004ed294a314282441904ee8d0b7234c082ef33

f54ea9a642fe043c264c1dbc2b440676ff19d8b4133ae4b7c6541da26e57ca76

4c15a76a0c9ec2c7fc3e9b70eaca8ea65e90b334830766274217c9e8369656bb

42945e0f7e7e92f3470ce17445d0502bc0cfcce20ba99bb95160364856c5edaa

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

Campaign

RLMA-2025-04793GENERIC-standard-pypi-install-pentestRLUA-2026-00560

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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