Which versions of tronapinet are malicious?

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

How do I remediate tronapinet if I installed it?

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

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

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

Malicious package

tronapinetPyPI

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

MAL-2025-6605

Immediate action

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

pip uninstall tronapinet

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)

40dc83590b79fe3c463d17857b29c62b639afac2c7dc1dce3e8123360040bdaa

ed20ac2b7e28ead94e54e5088108c02555d29dd061f449bd5654d1e66be20a04

ebb37f42f335b4a5f11e5e9bdb43390d3ba72478ee5c0ffa12c39f0e5226dd3b

6478acb7f1db10f41a984073fd2f65d1c58376bc4e796f25a530ca39c8a068b5

59c72181d1a58048c370a79d4a6bc7bf4649c26fd6432732b329272d3c2ac189

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 tronapinet (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tronapinet across your stack and pipelines.
If you installed it — respond
tronapinet 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 tronapinet 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 tronapinet 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. tronapinet 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

RLMA-2025-037042025-04-tronixRLUA-2026-00838

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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