Which versions of jmdrs are malicious?

The following PyPI versions of jmdrs are flagged malicious: 1.0.4, 1.0.5, 1.0.6. Treat any of these as compromised.

How do I remediate jmdrs if I installed it?

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

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

Yes — jmdrs is associated with the RLMA-2025-03623, RLUA-2025-04186, RLUA-2025-04779, RLUA-2025-05612 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 jmdrs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jmdrs (3 malicious versions).

Malicious package

jmdrsPyPI

Advisory published Jul 31, 2025Updated Dec 2, 2025

jmdrs is a confirmed malicious PyPI package (MAL-2025-6530) that executes malicious code on install (malicious versions 1.0.4, 1.0.5, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jmdrs (PyPI)

MAL-2025-6530

Immediate action

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

pip uninstall jmdrs

Malicious versions

3 flagged

1.0.41.0.51.0.6

Indicators of compromise (SHA-256)

cfcbc414976134a332304e31208508bf7072da25c1c4dbf153ba50684537a878

5f36897c38283e43996b0651a64adf83874442900ad83151f81361e63ff8af51

7dad5c23e35133db1253c744f0d1aaa7427bb683f0ae1a46089fedce9d1ede5a

588368c283cf14278ce6242393037645d599bef9290e90e35f1a5f585f68090c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-03623RLUA-2025-04186RLUA-2025-04779RLUA-2025-05612

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database