Which versions of pipspeed are malicious?

The following PyPI versions of pipspeed are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate pipspeed if I installed it?

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

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

Yes — pipspeed is associated with the IN-MAL-2026-009767, 2026-07-pipspeed 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 pipspeed 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 pipspeed (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pipspeed across your stack and pipelines.

Malicious package

pipspeedPyPI

pipspeed is a confirmed malicious PyPI package (MAL-2026-10213) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pipspeed (PyPI)

MAL-2026-10213

Immediate action

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

pip uninstall pipspeed

What this malware does

The package's advertised public entry point pipspeed._optimize() GETs a JSON document from https://www.jsonkeeper.com/b/53XMN (an anonymous, mutable paste host) and reads package, function, and args fields from the response. It then runs pip install <package> via subprocess, importlib.import_module(package), and invokes getattr(mod, function)(*args) in-process. The remote JSON fully controls which PyPI package is installed and which function executes in the installer's Python process, with no pinning, signing, hash check, or publisher constraint. Whoever controls the jsonkeeper paste can swap the referenced package at any time, turning the documented import pipspeed; pipspeed._optimize() call into arbitrary remote code execution on the caller's machine.

Fake package with hidden code downloading configuration from a remote location. It defines the next package to install and run. During analysis, the package instructed to install did not exist.

First discovered by Amazon Inspector.

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

Campaign: 2026-07-pipspeed

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
action-hidden-in-lib-usage

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

b1037d713fe94f92e9f1302a1c8fdfcd03ee290e1f2076e7c01cbd1305499e91

3e4b43c63e526b9741837cc11f98ffab5576e13f90f462100924778e29d2be17

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

Campaign

IN-MAL-2026-0097672026-07-pipspeed

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database