Which versions of speedd-testing-bot are malicious?

The following PyPI versions of speedd-testing-bot are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate speedd-testing-bot if I installed it?

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

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

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

Malicious package

speedd-testing-botPyPI

Malicious code in speedd-testing-bot (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191876

Immediate action

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

pip uninstall speedd-testing-bot

What this malware does

The package, distinguished as a speed testing or typosquatted Telegram library, contains a Telegram bot to perform remote control of the computer

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

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

8b4d3ec5703e4b8137b2a14ba931c94f6fa99282a52b0e084f23774d8f9527c8

b2c8226bceca5e4ecb7950563c129411c4541487f265f417a358bb42170357dd

2aaec37a58d7717b510aa569770af696e33ae7f9a59e733af3d6341d712f0d66

1329244d3e5dfdef07b3cc834eeb8bcf8765f76ac8351b1af6350bfe293be678

e50af7aaba81cf32521bbe78eabde8e358e8721b0a599287f6bf4a32c50b6545

476a2ea3c5babf4b9efb0534f42f9ccf56287a8db0eceb2674abd6eaa929e060

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

Detect & block this

O3 blocks speedd-testing-bot-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