# MAL-2026-13607: Malicious code in speed-hashes (PyPI)


- **Type:** Malicious package
- **Package:** `speed-hashes` (PyPI)
- **Published:** 7 Aug 2026

## What is MAL-2026-13607?

MAL-2026-13607 is a malicious package in speed-hashes, published on 7 Aug 2026. 

### Official description

setup.py defines a custom install command (NativeInstall) that runs on pip install. After the normal install step, a base64 literal (_COMPAT_PAYLOAD) is decoded and passed to exec(compile(...)) under cover-story names (_configure_native_bindings, NativeInstall) mimicking native-extension setup. The decoded Python code, on Linux, downloads an opaque binary from github.com/totti2188/8gp1Q7iZD3h4VW/releases/download/v1.3A/something to /tmp/something, chmods it 0755, and spawns it detached. Publisher metadata references github.com/nickolasburr/fast-hashes, which does not match the download source. The install lifecycle auto-executes attacker-controlled code fetched from a non-publisher GitHub account, yielding remote code execution on the installer's host.

Package imitates name of a popula library. During installation, obfuscated code downloads a malicious executable and starts it. It then exfiltrates at least cryptocurrency wallet data, probably more.

---

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

Campaign: 2026-08-flasq

Reasons (based on the campaign):

 - typosquatting

 - The package overrides the install command in setup.py to execute malicious code during installation.

 - exfiltration-generic

 - Downloads and executes a remote executable.

 - obfuscation

 - exfiltration-crypto

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

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-13607 is a malicious package: speed-hashes (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-13607/ (Markdown: https://insights.sbomify.com/MAL-2026-13607/index.md)
```

## Sources

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

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