Which versions of wallettron are malicious?

The following PyPI versions of wallettron are flagged malicious: 0.2.0. Treat any of these as compromised.

How do I remediate wallettron if I installed it?

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

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

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

Malicious package

wallettronPyPI

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

MAL-2025-6619

Immediate action

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

pip uninstall wallettron

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.2.0

Indicators of compromise (SHA-256)

e0dc49c0e23d0af0b0e6c5ef003a50f67f48c552a4ad20225f6bc8c2669d951c

c89cdd81b7f2f14d54941ff84424504c678638f3662faf326eccde495a3fd106

daa2901c8248d9a4e63be69c1595134618d563065c67a466b006d53bd92d5ce5

28633ec36c02ec286e56afc7b8042e1290db1a4561c555647f8c0442d548ba20

3f28316bee6191a4b3b11cf4890ffa771a66d02346b107279279fa838f803764

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

Campaign

RLMA-2025-037182025-04-tronixRLUA-2026-00906

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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