Which versions of urllib-slim are malicious?

The following PyPI versions of urllib-slim are flagged malicious: 9.31, 9.32, 9.33, 9.34, 9.35, 9.36. Treat any of these as compromised.

How do I remediate urllib-slim if I installed it?

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

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

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

Malicious package

urllib-slimPyPI

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

MAL-2026-1225

Immediate action

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

pip uninstall urllib-slim

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

6 flagged

9.319.329.339.349.359.36

Indicators of compromise (SHA-256)

ab38fb394a17f30f0503cdeb9f982f99aaec2c5f43496b6e5d7ccd505d926915

af9dfb22d0369590148408b736b7cdc45bf01c59f22fe6ee498809384081c452

acbcedbcc1d5bafffbb66128eae99b1fdc6c8e62b65bedd8f62ee2790919d972

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 urllib-slim (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging urllib-slim across your stack and pipelines.
If you installed it — respond
urllib-slim 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 urllib-slim 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 urllib-slim 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. urllib-slim on PyPI has been identified as a malicious package (versions 9.31, 9.32, 9.33, 9.34, 9.35, 9.36 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 urllib-slim-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