Which versions of hashtools32 are malicious?

The following PyPI versions of hashtools32 are flagged malicious: 1.0.0, 2.1.0. Treat any of these as compromised.

How do I remediate hashtools32 if I installed it?

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

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

Yes — hashtools32 is associated with the 2026-02-hashtools32, RLMA-2026-00378 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 hashtools32 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 hashtools32 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hashtools32 across your stack and pipelines.

Malicious package

hashtools32PyPI

Malicious code in hashtools32 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-1080

Immediate action

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

pip uninstall hashtools32

What this malware does

During import, the package attempts to exfiltrate sensitive Telegram session files

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

Campaign: 2026-02-hashtools32

Reasons (based on the campaign):

exfiltration-credentials
files-exfiltration

Malicious versions

2 flagged

1.0.02.1.0

Indicators of compromise (SHA-256)

689514b83cd6496b0a4213d26325e73cd2c4f0e19128b969d19797bcdd4b131d

09c9db1ee500166c34dca9d69cdee7100921741b3ef42a6d96c0ec7ce1f319f7

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

Campaign

2026-02-hashtools32RLMA-2026-00378

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

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