Which versions of medoen are malicious?

The following PyPI versions of medoen are flagged malicious: 0.1.1. Treat any of these as compromised.

How do I remediate medoen if I installed it?

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

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

Yes — medoen is associated with the RLMA-2025-04791, 2025-08-k7eel, RLUA-2026-00510 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 medoen across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for medoen (version 0.1.1).

Part of a larger attack: 2025-08-k7eel published 31 malicious packages. See the full campaign →

Malicious package

medoenPyPI

Advisory published Aug 21, 2025Updated Mar 19, 2026

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

Malicious code in medoen (PyPI)

MAL-2025-47786

Immediate action

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

pip uninstall medoen

What this malware does

Importing the module downloads and executes widely recognized malware

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

Campaign: 2025-08-k7eel

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.1

Indicators of compromise (SHA-256)

95d531f2ebb879356a200815bba845c045c8e42616a71bf6f9425065dbbc536c

a7ee8662b543a35d831490d09f9389a0fa563df89fd124088d0651bcaacaa6a0

f0fcf26f9d33d1a5d868d0637274af9fa3be00737221aaef0cbc596e1fc39f9a

a3e26313caf324d12c5598085f2bb641d777ab30f8485606d8419eb1c91879fb

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-047912025-08-k7eelRLUA-2026-00510

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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