# MAL-2026-10213: Malicious code in pipspeed (PyPI)


- **Type:** Malicious package
- **Package:** `pipspeed` (PyPI)
- **Published:** 12 Jul 2026

## What is MAL-2026-10213?

MAL-2026-10213 is a malicious package in pipspeed, published on 12 Jul 2026. 

### Official description

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

## What should I do about MAL-2026-10213?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10213 is a malicious package: pipspeed (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10213/ (Markdown: https://insights.sbomify.com/MAL-2026-10213/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10213

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10213/
Summaries are generated and may contain mistakes; the official description above is the record.