Which versions of urlsser are malicious?

The following PyPI versions of urlsser are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate urlsser if I installed it?

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

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

Yes — urlsser is associated with the 2025-10-speedd-testing-bot 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 urlsser across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for urlsser (version 0.2).

Part of a larger attack: 2025-10-speedd-testing-bot published 26 malicious packages. See the full campaign →

Malicious package

urlsserPyPI

Advisory published Jan 22, 2026Updated Jul 20, 2026

urlsser is a confirmed malicious PyPI package (MAL-2026-468) that steals credentials and exfiltrates sensitive data (malicious version 0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in urlsser (PyPI)

MAL-2026-468

Immediate action

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

pip uninstall urlsser

What this malware does

This package does not directly contain malicious code, but was uploaded as part of the malicious campaign and is used as a helper in further infection stages.

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

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote malicious script.
rat

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

c4f6d5a2656d3741fd7a1a4c50a9d3332a09874ef7c46713d0ad5e36478a063e

9de2e5aa4728aa497d62b414eebd009b8ea2b4449ab507834334531adcb04408

00a935ffcfbb05edec9e227519f97daf4068a48264d6d1c6f4a14743f69560ba

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for urlsser (version 0.2).
If you installed it — respond
urlsser 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 urlsser 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. urlsser on PyPI has been identified as a malicious package (version 0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-10-speedd-testing-bot

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database