Which versions of computestpspeedcompcomp are malicious?

The following PyPI versions of computestpspeedcompcomp are flagged malicious: 0.5. Treat any of these as compromised.

How do I remediate computestpspeedcompcomp if I installed it?

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

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

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

Malicious package

computestpspeedcompcompPyPI

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

MAL-2025-191705

Immediate action

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

pip uninstall computestpspeedcompcomp

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.5

Indicators of compromise (SHA-256)

1c5463d4f932afe39b8c66c89bc1f3000488566cd62f8394808803fd7c5138ea

559d64721f5c40906b8c1ba33cf19ffb4a4ae4de9837c442be7c54a0ba1b3b6d

61e051b9f9c6804ef96457331046797dcbccbacbfb444eb564cc1f72eae576c2

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 computestpspeedcompcomp (version 0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging computestpspeedcompcomp across your stack and pipelines.
If you installed it — respond
computestpspeedcompcomp 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 computestpspeedcompcomp 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 computestpspeedcompcomp 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. computestpspeedcompcomp on PyPI has been identified as a malicious package (version 0.5 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 computestpspeedcompcomp-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