Which versions of urlsssser are malicious?

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

How do I remediate urlsssser if I installed it?

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

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

Yes — urlsssser 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 urlsssser across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

urlsssserPyPI

Advisory published Jan 22, 2026Updated Jul 20, 2026

urlsssser is a confirmed malicious PyPI package (MAL-2026-470) 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 urlsssser (PyPI)

MAL-2026-470

Immediate action

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

pip uninstall urlsssser

What this malware does

Package does not contain malicious code, but was published as a part of the malicious campaign and is used during 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)

242b446cd6cce908f668bfc1b199aa8f54a9ee1138b399ea6012f3b2bd2624e8

6a2299f14c9cf03758ced47a419146568a7cb7268d8d80708fea2dc65650e569

057ae44ed213551caf659152c9a761ce6bb5031b3ee8db3510390175a5ada8cd

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for urlsssser (version 0.2).
If you installed it — respond
urlsssser 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 urlsssser 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. urlsssser 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 urlsssser-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