Which versions of trongitpy are malicious?

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

How do I remediate trongitpy if I installed it?

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

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

Yes — trongitpy is associated with the RLMA-2025-04816, 2025-04-tronix, RLUA-2026-00842 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 trongitpy 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 trongitpy (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 trongitpy across your stack and pipelines.

Malicious package

trongitpyPyPI

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

MAL-2025-47806

Immediate action

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

pip uninstall trongitpy

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)

8152f58f4bdc931db65529d1a3c5daad4768b7ec4c595c50c00edeed6e52e1c1

cc5e37b3728264cd56032704ceeaf37ed9e38b537d37086947df959a3c8adb20

e52bd087b815590884e004c2db67e0dd137ff0230282e4eb2b27afcb11ed36c3

d063318398b7e8a88cef67843437db9a80daf0c7964ae018a012ad64523bb775

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 trongitpy (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 trongitpy across your stack and pipelines.
If you installed it — respond
trongitpy 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 trongitpy 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 trongitpy 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. trongitpy 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-048162025-04-tronixRLUA-2026-00842

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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