Which versions of speedtestpython are malicious?

The following PyPI versions of speedtestpython are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate speedtestpython if I installed it?

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

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

Yes — speedtestpython is associated with the RLMA-2025-02001, 2025-02-multis, RLUA-2026-00774 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 speedtestpython 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 speedtestpython (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging speedtestpython across your stack and pipelines.

Malicious package

speedtestpythonPyPI

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

MAL-2025-3002

Immediate action

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

pip uninstall speedtestpython

What this malware does

Infostealer with multiple possibilities, but not auto-activating on installation. There are already multiple attempts to publish it, with different innocent-looking names.

The campaign contains the with Infostealer itself and packages that include it as dependency and triggered.

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

Campaign: 2025-02-multis

Reasons (based on the campaign):

infostealer
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

1c029624329a6ca4a290497505d6ce7cb9b2c70d0442593ce4f721dcb6381907

95124703447032ea7a355bd9e0cdfb42354e99d21b7b18768736c209e55b420d

e6f351fd3b705c5c3ec61271d7b892158082a255cc25065da833f06f336b29f6

4067aff85e2f95b6fc16e8a448357e7bf2d332822a749e7769792cb550426d23

a26ff475106f856bf9c23c709e719b05751ab93fa049cc72a4aaea74a63024b1

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 speedtestpython (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging speedtestpython across your stack and pipelines.
If you installed it — respond
speedtestpython 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 speedtestpython 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 speedtestpython 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. speedtestpython on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-020012025-02-multisRLUA-2026-00774

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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