Which versions of evil-pkg2 are malicious?

The following PyPI versions of evil-pkg2 are flagged malicious: 0.2, 0.3. Treat any of these as compromised.

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

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

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

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

Malicious package

evil-pkg2PyPI

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

MAL-2025-2961

Immediate action

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

pip uninstall evil-pkg2

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

2 flagged

0.20.3

Indicators of compromise (SHA-256)

374453a4f6e085b592f8b244146b4f1f6f3ff6be667d4cb49f4cc89a72756c66

0bc093a5b181fc098ac0340b3842eec0235c04ee470746759f25fb89ee30ec88

d1e1a7a65c4f1287f792371642eb66734028aa9dc7ffc50adde9b551e082bdb1

76b237419286403d49ace6522d44ed518ec79d29ea6adea604b1869f42c2467d

57ba871f57ec4f18112c590a5f2faed65e221e8ce6ff237c1645b58141cc5ef8

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

Campaign

RLMA-2025-01959GENERIC-simple-testsRLUA-2026-00304

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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