Which versions of evil-rce2 are malicious?

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

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

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

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

Yes — evil-rce2 is associated with the 2025-12-evil-rce 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-rce2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for evil-rce2 (version 1.0.0).

Malicious package

evil-rce2PyPI

Advisory published Dec 6, 2025Updated Dec 6, 2025

evil-rce2 is a confirmed malicious PyPI package (MAL-2025-192362) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in evil-rce2 (PyPI)

MAL-2025-192362

Immediate action

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

pip uninstall evil-rce2

What this malware does

Running the module starts a reverse shell

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

Campaign: 2025-12-evil-rce

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

63a6a4d1f5ad55b3b2b836b95a7153f322bb4ea2f718f665a51a4a94f32576d5

Detection & response playbook

Credential / info stealer

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

Campaign

2025-12-evil-rce

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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