Which versions of hexdeclink are malicious?

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

How do I remediate hexdeclink if I installed it?

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

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

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

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

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

Malicious package

hexdeclinkPyPI

Advisory published Dec 1, 2025Updated Dec 24, 2025

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

MAL-2025-191757

Immediate action

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

pip uninstall hexdeclink

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)

5614113ca969ec3f951b1ddc687fab99bd154c8982a623428c26a0d0bb8c9902

4df8ddadb082a2d285b508fc17356d22ef0375649424cc39d9b08a9e32ab6684

cfebc5d414f6860c0ada77685ba9e31f35d6c1231575290cdb46cf772f7299db

Detection & response playbook

Credential / info stealer

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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