Which versions of randpicker are malicious?

The following PyPI versions of randpicker are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate randpicker if I installed it?

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

If randpicker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is randpicker part of a known attack campaign?

Yes — randpicker is associated with the 2026-06-old-randpicker 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 randpicker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for randpicker (version 0.1.0).

Malicious package

randpickerPyPI

Advisory published Jun 18, 2026Updated Jun 18, 2026

randpicker is a confirmed malicious PyPI package (MAL-2026-6138) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in randpicker (PyPI)

MAL-2026-6138

Immediate action

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

pip uninstall randpicker

What this malware does

When calling the Email function, the code creates a backdoor script and attempts to achieve persistence. The script connects to a Telegram bot and awaits commands to execute.

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

Campaign: 2026-06-old-randpicker

Reasons (based on the campaign):

action-hidden-in-lib-usage
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
backdoor
uses-telegram-bot
persistence
peristence-autorun

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

378d07b700aa25d356594d7b1c42db107def3dbd1cce734e4c1c50b411048eb6

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for randpicker (version 0.1.0).
If you installed it — respond
randpicker 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 randpicker was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. randpicker on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-06-old-randpicker

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database