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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for urlsser (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging urlsser across your stack and pipelines.

Malicious package

urlsserPyPI

Malicious code in urlsser (PyPI) Remove it immediately and rotate any exposed credentials.

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

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