Which versions of hashidf are malicious?

The following PyPI versions of hashidf are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate hashidf if I installed it?

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

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

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

Malicious package

hashidfPyPI

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

MAL-2025-6520

Immediate action

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

pip uninstall hashidf

What this malware does

If ran as a module, the package silently starts a binary hidden in a txt file in the background. At the moment, it appears to be PuTTy, and without additional instruction it does not do anything, but it is clearly a preparation for malicious actions.

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

Campaign: 2025-06-hashidf

Reasons (based on the campaign):

obfuscation
typosquatting

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

3c4fe8181b2a1e5e644418e023c13aa25b6fdb7690e67222c26f0c5f46434628

d8e6a625ca054543f793c66550646f9d5b3ffeb5f1d6ecbaa0ba8be5136fc829

126b111d14601f2ff653938378c5e6d0f534439f0eac8db7984dfe7aa0f20b52

a935910c59e71cb6745f0e2276acf5e58774fbcf991f0cbfcabde988a4ea91c3

df50f65ab75cfc384839a05aae92224507ab8fb86f0ca9febb395738b591803e

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

Campaign

RLMA-2025-036122025-06-hashidfRLUA-2026-00377

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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