Which versions of risk-utilities are malicious?

The following PyPI versions of risk-utilities are flagged malicious: 6.0.0, 6.0.1. Treat any of these as compromised.

How do I remediate risk-utilities if I installed it?

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

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

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

Malicious package

risk-utilitiesPyPI

Malicious code in risk-utilities (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1223

Immediate action

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

pip uninstall risk-utilities

What this malware does

During installation, the package starts obfuscated code that downloads and runs remote executables in specific environments. In some packages in the campaign, the code only attempts to exfiltrate some basic information using DNS requests and then likely cover tracks by installing a similarly named package from private repository

Related campaigns: 2026-02-spark-audit-notify, 2026-03-geekennedy

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

Campaign: 2026-02-urllib-slim

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote executable.
obfuscation
dependency-confusion

Malicious versions

2 flagged

6.0.06.0.1

Indicators of compromise (SHA-256)

e348257ce9a3bae45ebd2659c04fbfea50b94293533efd04ce326900921fd130

b2fd5ee5125e623ac64304c210f37c85d220b214f5102c2df2beb781e37178af

22f9a9b921e53b4755c41241969fcc8b410b09f29a63ed9c23c5a19c966b4946

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

Campaign

2026-02-urllib-slim

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks risk-utilities-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