Which versions of compute-st-speed are malicious?

The following PyPI versions of compute-st-speed are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate compute-st-speed if I installed it?

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

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

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

Malicious package

compute-st-speedPyPI

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

MAL-2025-191703

Immediate action

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

pip uninstall compute-st-speed

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)

a8e244f4b85820c3cd6ec50f3db54a03ffaf96c9d6e451c60490584245cd043f

35e058e2655bdae9fb5cef9e594f9f1dcc59206620e758c625c9cdee1e0634a8

4997fc53def0c9edc50f9a19b704b6518ed580ad6b953f4e390c0d93b313cd1f

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

2025-02-multis

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks compute-st-speed-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