Which versions of speed-testing-nt are malicious?

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

How do I remediate speed-testing-nt if I installed it?

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

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

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

Malicious package

speed-testing-ntPyPI

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

MAL-2025-191874

Immediate action

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

pip uninstall speed-testing-nt

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)

14f71a5e1c95dc16961814e9fed0f6f623ab6fc101b57cdd308aac600e48a52d

2e5f8accca3f5615e1e9802693f180b7d8fd0e648741b8dc987460ffcd87c309

dcfc1b92868e7f4eef0f4c0e901418a557089fe5269a1e4ef07725d397cddbb3

a7bf2a1eb8f2f65fa8cd8a682cfd79f271d87b1c9e3472a3b3f2d625ffcac3e0

7f5ad885ce4871d4d7db6d3cd009393cc6e53c998efd6954bcf17b5dc3ab1ba5

42bc3efbce8fa37787d1e2800a053a7973520d2123369f1da7ef231604f5edee

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