Which versions of hexadec are malicious?

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

How do I remediate hexadec if I installed it?

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

If hexadec was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hexadec part of a known attack campaign?

Yes — hexadec is associated with the 2025-04-tronix, RLMA-2025-06566, RLUA-2026-00388 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 hexadec across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hexadec (version 0.0.1).

Part of a larger attack: 2025-04-tronix published 67 malicious packages. See the full campaign →

Malicious package

hexadecPyPI

Advisory published Nov 14, 2025Updated Mar 19, 2026

hexadec is a confirmed malicious PyPI package (MAL-2025-191753) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hexadec (PyPI)

MAL-2025-191753

Immediate action

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

pip uninstall hexadec

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

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6cf9dc7beea9e0b0b7cf68a0aaaef323a26a58952e4a659b3ba20deee2023ded

f9d0ae8ccf24a6f5bfc3a0d5e39a983576d6edb2c64d9fe31fcb758236a4aa25

ca866d4245ec47c185cd565690c1b7461ca90b5c0c1ff789f71b7cd9893c68e0

7b2b65cb7dbbbc6dc7faca373ff260badb48831858811418e233c2d70e781a6d

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hexadec (version 0.0.1).
If you installed it — respond
hexadec 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 hexadec was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hexadec on PyPI has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-tronixRLMA-2025-06566RLUA-2026-00388

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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