Which versions of evil-pkg are malicious?

The following PyPI versions of evil-pkg are flagged malicious: 0.1. Treat any of these as compromised.

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

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

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

Yes — evil-pkg is associated with the RLMA-2025-01957, GENERIC-simple-tests, RLUA-2026-00302 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-pkg 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 evil-pkg (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evil-pkg across your stack and pipelines.

Malicious package

evil-pkgPyPI

Malicious code in evil-pkg (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-2959

Immediate action

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

pip uninstall evil-pkg

What this malware does

Packages that might be part of testing for pentesting / malicious activity / joy, with suspicious activity that does not present any real harm.

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: GENERIC-simple-tests

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

5d757f156495cc977a74e261d644d9002e32680ed5279583bbb22b9dd6d4bee8

1800e8ca65a45d816eafc4d336142aad92472f617ae84018d31dbffece4552c9

366920f1b216795839a0a8533db122155f0c839032a67fdd6a33544179749a2c

153ac9b1dd3236fa2d7fb8a976942256e317f234878c719ff71a07c61eb3e014

388c27b2933eca8e4d04f38bb797ad169d93b538ab237d1c711ae39a401c194c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for evil-pkg (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging evil-pkg across your stack and pipelines.
If you installed it — respond
Remove evil-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-pkg 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 evil-pkg 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. evil-pkg on PyPI has been identified as a malicious package (version 0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-01957GENERIC-simple-testsRLUA-2026-00302

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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