Which versions of fast-hashes are malicious?

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

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

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

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

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

Malicious package

fast-hashesPyPI

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

MAL-2026-13490

Immediate action

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

pip uninstall fast-hashes

What this malware does

setup.py defines a custom install command (NativeInstall.run) that decodes a base64 blob and passes it to exec(compile(...)) at install time. The decoded payload downloads an opaque binary from https://github.com/totti2188/8gp1Q7iZD3h4VW/releases/download/v1.3A/something to /tmp/something, chmods it to 0755, and Popen-launches it detached with start_new_session=True. The fetch target's GitHub account (totti2188) is unrelated to the declared package publisher, the binary is unpinned and unverified, and the fetch-and-execute logic is concealed behind a base64 blob labeled _COMPAT_PAYLOAD with a benign-sounding '_configure_native_bindings' cover story. The package's non-install code only wraps hashlib and has no legitimate need for a native binary. Any pip install of this version triggers arbitrary code execution on the installer's host under the identity of a third-party GitHub account.

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)

658a96d4157086ae099c38b27ef8fb7d1664956a251f21d55a9d8cb208c0a8fc

39a077e7478e5e60661ac52b41882f4f72d91acd6777a1828f2aa28d5ccfb2ba

503b750458783954b66f8dea6ee8b0300fd7db5b225280f1af432cf78c1faf6d

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 fast-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 fast-hashes across your stack and pipelines.
If you installed it — respond
fast-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 fast-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 fast-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. fast-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

2026-08-flasqIN-MAL-2026-016909

References

Credits

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

Detect & block this

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