Which versions of mumupatcher are malicious?

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

How do I remediate mumupatcher if I installed it?

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

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

Yes — mumupatcher is associated with the RLMA-2024-11095, 2024-08-embeds-RealtekHDAudioManager, RLUA-2026-00539 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 mumupatcher across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for mumupatcher (version 0.0.1).

Part of a larger attack: 2024-08-embeds-RealtekHDAudioManager published 40 malicious packages. See the full campaign →

Malicious package

mumupatcherPyPI

Advisory published Sep 4, 2024Updated Mar 19, 2026

mumupatcher is a confirmed malicious PyPI package (MAL-2024-11639) 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 mumupatcher (PyPI)

MAL-2024-11639

Immediate action

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

pip uninstall mumupatcher

What this malware does

Importing a module starts downloading and executing an infostealer, widely identified by AV/sandboxes.

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

Campaign: 2024-08-embeds-RealtekHDAudioManager

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b780ac24a9b45e127f8a95f79f35c7a415ea53a45898574432bb04de5a203aac

778c53c1e5e3d4b97763ec500a0e329c4b0ddd8551fea972ae392ccbd53d5053

c629884f1972a86de285e5eda36f8ec8358c1b40d22922ad309a11174af5fca4

adbf0e4c3c345d55b81e5d1972a28aca353a2f2e3570cc67abea138da5b58b36

3e4ec3c12c8639cca5ba3ceea09163b9187fa877222739ea4206522f1d223955

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for mumupatcher (version 0.0.1).
If you installed it — respond
mumupatcher 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 mumupatcher 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. mumupatcher 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-2024-110952024-08-embeds-RealtekHDAudioManagerRLUA-2026-00539

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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