Which versions of torhc are malicious?

The following PyPI versions of torhc are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate torhc if I installed it?

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

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

Yes — torhc is associated with the RLMA-2024-11191, 2024-09-bondonioanderas-cryptominer, RLUA-2026-00832 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 torhc 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 torhc (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging torhc across your stack and pipelines.

Malicious package

torhcPyPI

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

MAL-2024-11732

Immediate action

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

pip uninstall torhc

What this malware does

During installation, a cryptominer is secretly installed and started.

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

Campaign: 2024-09-bondonioanderas-cryptominer

Reasons (based on the campaign):

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

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

74161e8d53afa30730dffd346c40d6b02d650788784740bcf64ef24d323db50f

b6df01c26a3d1c7009b1370ea05efc0fbf98317f5d36e7c4e7b35877d78cb82e

385cb451ed567a10096fce231790d6a9bce59bb47c8d7bdfff5a8f4aaa0854ed

d9e1ae340dabc14900487ed60c98e5f8bbc124fd011d0e630e31e428ce2cdb8c

302519140a93ac6b4dc296985eb16cf8b53236d750af695a71d11fa1978ab769

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

Campaign

RLMA-2024-111912024-09-bondonioanderas-cryptominerRLUA-2026-00832

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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