Which versions of permsupping are malicious?

The following PyPI versions of permsupping are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate permsupping if I installed it?

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

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

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

Malicious package

permsuppingPyPI

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

MAL-2025-41717

Immediate action

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

pip uninstall permsupping

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

80d9e5da205273efc549849a1ed02b97c731ec9a41dc2ca02794f541c8245e55

939d0d2d02d012e4b3c17fee62fd3ebe1991e767717a8f7201ac114303cc4486

2dec8af74032aa8a44855e36075b08f5a83aef64962e2c6604e6ecb0b288aa10

a3cf8c231d342c0955a1ec7ff2bb45fd0eb868ea52026ef7712b86f41e05fd58

213c96ebe5c08e80dceb219f990a8329b3ff35a087d7f36dfb8765ce0fa0d09d

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

Campaign

RLMA-2025-042122025-08-tronapisyncRLUA-2026-00589

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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