Which versions of mirage-rce are malicious?

The following PyPI versions of mirage-rce are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate mirage-rce if I installed it?

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

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

Yes — mirage-rce is associated with the RLMA-2025-01973, 2025-02-mirage-rce, RLUA-2026-00523 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 mirage-rce across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mirage-rce (version 0.0.1).

Malicious package

mirage-rcePyPI

Advisory published Mar 2, 2025Updated Mar 19, 2026

mirage-rce is a confirmed malicious PyPI package (MAL-2025-2975) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mirage-rce (PyPI)

MAL-2025-2975

Immediate action

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

pip uninstall mirage-rce

What this malware does

Setup.py contains a reverse shell

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

Campaign: 2025-02-mirage-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

0.0.1

Indicators of compromise (SHA-256)

9a8ec5d1258e90f9dbbf90175f3e40ef38ca58cae2b5b2e048bd34045e25044b

9335196ccce03f70d20f319760081a6a4d5549bfbe6a733be38084890bbc03f6

f9ba7e438828f3bcacd252bc54f00732b129fe6fc8f6a9909d964720ac1e6420

28fad7d114fd99e403c318ae35e13024582b3211e1a5e050814d389bdd1236be

af0bafdf3a203e82a1bf325412ab1cd59785ab0c7928eb73294b3246974a82cf

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-019732025-02-mirage-rceRLUA-2026-00523

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks mirage-rce-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