Which versions of hexdecimal are malicious?

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

How do I remediate hexdecimal if I installed it?

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

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

Yes — hexdecimal is associated with the 2025-04-tronix 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 hexdecimal across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

hexdecimalPyPI

Advisory published Nov 2, 2025Updated Dec 3, 2025

hexdecimal is a confirmed malicious PyPI package (MAL-2025-191756) 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 hexdecimal (PyPI)

MAL-2025-191756

Immediate action

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

pip uninstall hexdecimal

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)

73e647f9fd262e646ee9cfd93a4314601147585e9eb71eebf05fb633eeff89cc

c76fe38c65db757a8e7f52d36acea2c85ea223e1342e513c0eb2115b19da7bcb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for hexdecimal (version 0.0.1).
If you installed it — respond
hexdecimal 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 hexdecimal 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. hexdecimal 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-tronix

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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