Which versions of trongridperm are malicious?

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

How do I remediate trongridperm if I installed it?

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

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

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

Malicious package

trongridpermPyPI

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

MAL-2025-41789

Immediate action

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

pip uninstall trongridperm

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)

323195e2b34d0b25a743c640086788e8fbf4d27e6e08d85ddba4e148c3fd33d8

2f31334bc0583d106e739a7300059f29b33e0aeef9f949fcfc29fdbbff1a48de

eb2deee7747ccb12e0b2da45c212a0678fc8a3f02bf72b8aba4508ae70e3e26a

77aa730d26597931d0bf90d7b1e9ae67b6ddb8e4b39314453df0e432e1357608

93fd4e0c69babf962120ebc9300faa6e8a1021136fe692ad5b437ed34b4acb84

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

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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