Which versions of urllib33 are malicious?

The following PyPI versions of urllib33 are flagged malicious: 1.27.15. Treat any of these as compromised.

How do I remediate urllib33 if I installed it?

Remove urllib33 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed urllib33 — how do I know if it already compromised me?

If urllib33 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is urllib33 part of a known attack campaign?

Yes — urllib33 is associated with the RLMA-2024-04990, RLUA-2024-09472 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 urllib33 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for urllib33 (version 1.27.15).

Malicious package

urllib33PyPI

urllib33 is a confirmed malicious PyPI package (MAL-2024-6186) that executes malicious code on install (malicious version 1.27.15). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in urllib33 (PyPI)

MAL-2024-6186

Immediate action

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

pip uninstall urllib33

Malicious versions

1 flagged

1.27.15

Indicators of compromise (SHA-256)

a3f482798e86834b74ce342d77d3d5eb64131a4fa72912ec9e7db70f7375223c

994b40d19a18ce3f43b698840d9661f78c15d83a9752da019fc6ccb8e2370951

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for urllib33 (version 1.27.15).
If you installed it — respond
Remove urllib33 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If urllib33 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. urllib33 on PyPI has been identified as a malicious package (version 1.27.15 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04990RLUA-2024-09472

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks urllib33-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database