Which versions of rendom are malicious?

The following PyPI versions of rendom are flagged malicious: 0.2. Treat any of these as compromised.

How do I remediate rendom if I installed it?

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

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

Yes — rendom is associated with the 2025-10-speedd-testing-bot 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 rendom 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 rendom (version 0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rendom across your stack and pipelines.

Malicious package

rendomPyPI

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

MAL-2025-192323

Immediate action

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

pip uninstall rendom

What this malware does

The package contains a Telegram bot to perform remote control of the computer. The package name additionally suggests typosquatting against standard random moduke

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

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

1 flagged

0.2

Indicators of compromise (SHA-256)

c0cc29ab946e5476954c07b3c8b4ee429ad6c84645a1b6b37cfe9a24c47c07b4

1effe6d94e0635864c22ea960a22b40294c3f2e510550046139bcd78f62a33fa

6343a9b4a929a5295de2eec183ae79488153e7d26c567be28079f162c768d632

c35c5bb8cf4e737b3695e8992c605d9c73d8767fc67d34ac0535d0f3c64f7684

83251dfcfe4ae108799df7479028a61def8b2154d543930631a0a79586cdf219

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

Campaign

2025-10-speedd-testing-bot

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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