Which versions of evil-package are malicious?

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

How do I remediate evil-package if I installed it?

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

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

Yes — evil-package is associated with the RLMA-2024-08254, TEST-PACKAGES, RLUA-2026-00301 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-package across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for evil-package (3 malicious versions).

Malicious package

evil-packagePyPI

Advisory published Jul 24, 2024Updated Mar 19, 2026

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

Malicious code in evil-package (PyPI)

MAL-2024-10023

Immediate action

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

pip uninstall evil-package

What this malware does

Category: PENTEST - Packages with high confidence of being created for a pentest.

Campaign: TEST-PACKAGES

Reasons (based on the campaign):

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

547ec54cea99925ceacfdc9a45a65648ac954c0a3dbe8f2c7249b373e842c354

ab19fa9ea094361c91cc61de34e9b9c01d35a514f1511f8f7ce62d5bbd65d91b

a6fe9e1f81afbcfb5f8f0d260af0434649c77b11d353d3264c7022e763767d43

391940fe0f66d0248dc84019d20b221a3340bd66a93e0639baabee249af6e9f3

c4ced34b36c49ff9a4b0d0b0da3ee67767d0dcab67b0142eca31aecf531fddf3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for evil-package (3 malicious versions).
If you installed it — respond
Remove evil-package 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-package 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-package on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-08254TEST-PACKAGESRLUA-2026-00301

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks evil-package-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