Which versions of hexdecpy are malicious?

The following PyPI versions of hexdecpy are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate hexdecpy if I installed it?

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

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

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

Malicious package

hexdecpyPyPI

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

MAL-2025-191631

Immediate action

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

pip uninstall hexdecpy

What this malware does

Package appears to be designed for private key exfiltration, but no known usage. The name appears to be related to the cryptocurrency TRX (Tron / Tronix). Some packages additionally clone the readme of other, legit libraries. The similar packages are repeating uploaded to PyPI

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

Campaign: 2025-04-tronix

Reasons (based on the campaign):

exfiltration-generic
crypto-related

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

d4f4c4313370041b22afc033950d6e010c87d7bd13eecc766c605bef42a9ba4d

b0f53ae1971db339e9383a0db92fe44f7de86800198a95d884bc971bad8e10f7

246a48191e6ca40c12a29dfd6b4d14307b5f478f7cbec5f99fb96f12e78c89aa

a60a1e1444c05fda6622e9ed4f2659c96cdb7a11ef9318c27d3e2829d247206d

a5e208f317c9ecc21a3b4a3bdac21b5ef263e4ec04388c9a72f537010eb3517e

b1ffddfcfc18a4c0aa2e6c6022ae44919cba9cb141db1cbc9b7aad249328ceb1

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

Campaign

RLMA-2025-056002025-04-tronixRLUA-2026-00392RLUA-2026-02072

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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