Which versions of hexdecli are malicious?

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

How do I remediate hexdecli if I installed it?

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

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

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

Malicious package

hexdecliPyPI

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

MAL-2025-191630

Immediate action

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

pip uninstall hexdecli

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)

d899bb657019a931f9aa0030a8c019de6e48e59654f3ca8ae82e2b6557359d0c

bb24d6d48574cfd05aeb232119e668536f683c44620d9a1a134b6ba3316cc771

14b72d96ce6a8700ee188783d301dc5f37cd7182ac8082491a75c582184309e4

603300f4ea975319369011ec971e0bfef2eb2eabc921f7f347d78664458478a9

b7ef6d67e30482e0a67034a1faf0c359814f27f2b27af611075341d68b2494b5

d1b22f079e93b399a45ab4dc97d5b8d13376cbceefda77831552d4e8809ab5f7

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 hexdecli (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hexdecli across your stack and pipelines.
If you installed it — respond
hexdecli 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 hexdecli 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 hexdecli 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. hexdecli 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-055992025-04-tronixRLUA-2026-00390RLUA-2026-02071

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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