Which versions of evil-select-pkg are malicious?

The following PyPI versions of evil-select-pkg are flagged malicious: 0.0.1, 0.0.2. Treat any of these as compromised.

How do I remediate evil-select-pkg if I installed it?

Remove evil-select-pkg from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed evil-select-pkg — how do I know if it already compromised me?

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

Yes — evil-select-pkg is associated with the 2024-09-old-evil-select-out 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 evil-select-pkg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for evil-select-pkg (2 malicious versions).

Malicious package

evil-select-pkgPyPI

Advisory published Sep 24, 2024Updated Dec 31, 2025

evil-select-pkg is a confirmed malicious PyPI package (MAL-2024-12266) that executes malicious code on install (malicious versions 0.0.1, 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in evil-select-pkg (PyPI)

MAL-2024-12266

Immediate action

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

pip uninstall evil-select-pkg

What this malware does

Package description attempts to pentest/exploit the PyPI web interface.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-09-old-evil-select-out

Reasons (based on the campaign):

other

Malicious versions

2 flagged

0.0.10.0.2

Indicators of compromise (SHA-256)

2b20dca3341dcf15ed5408898da5e7fac0f2d775d75f764f1804d4c60a837e90

db8225867ca74c2a2192382dc4abcc5119fb1ac07049412245e3a686524138f8

de7e5ebd75aeae14c9a5f445f30905e0876b710c7d9f508dd5d742f100dbfe92

cdff4873c4bb427846955c66392f7ccf6a482c240782b8a1237dbfafc266285d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for evil-select-pkg (2 malicious versions).
If you installed it — respond
Remove evil-select-pkg from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If evil-select-pkg 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. evil-select-pkg on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-09-old-evil-select-out

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks evil-select-pkg-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database