Which versions of tronapisync are malicious?

The following PyPI versions of tronapisync are flagged malicious: 0.1.1, 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate tronapisync if I installed it?

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

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

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

Malicious package

tronapisyncPyPI

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

MAL-2025-41787

Immediate action

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

pip uninstall tronapisync

What this malware does

Package is prepared to exfiltrate private keys, most probably for Tron cryptocurrency. There is no other purpose of the package

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-08-tronapisync

Reasons (based on the campaign):

exfiltration-crypto

Malicious versions

4 flagged

0.1.11.0.01.0.11.0.2

Indicators of compromise (SHA-256)

0101015ac62853bfac99b9c6aeb826024df508cc650f343ce1ede30925d6a2c7

fb8cfda49a47d8f3292983904c1b5a778a4947d3a141c530c55d4ac1b2e7d38b

2768edf78749b023b104efcbfcfedd4d2633480e8d19ee433d467e1b39d2b9ce

69d698be9c2529304ecdf6de17e7544ad8fab2b05507902a8bcfacfba3f0c9b7

0209664effe05a01c7c59512fcd8b2a92b28f82e4634fbd329e3416e09f4dec7

3b00f275fa783dd4a635e99dd640b5e56ca59bca185dc609ad562cbd2d2bc9c3

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

Campaign

RLMA-2025-042852025-08-tronapisyncRLUA-2026-00840

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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