Which versions of speed-hashes are malicious?

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

How do I remediate speed-hashes if I installed it?

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

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

Yes — speed-hashes is associated with the IN-MAL-2026-017054, 2026-08-flasq 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 speed-hashes 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 speed-hashes (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 speed-hashes across your stack and pipelines.

Malicious package

speed-hashesPyPI

speed-hashes is a confirmed malicious PyPI package (MAL-2026-13607) 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 speed-hashes (PyPI)

MAL-2026-13607

Immediate action

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

pip uninstall speed-hashes

What this malware does

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

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

120e6126065bccc254b925a6913422c0cbdd201054437820369c2726fd4a2871

6d9bfbd1f81612ac7e8f7da9226a520d3d8c76387f877a434466e9326f2079fe

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 speed-hashes (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 speed-hashes across your stack and pipelines.
If you installed it — respond
speed-hashes 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 speed-hashes 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 speed-hashes 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. speed-hashes 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-0170542026-08-flasq

References

Credits

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

Detect & block this

O3 blocks speed-hashes-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