Which versions of md5-en are malicious?

The following PyPI versions of md5-en are flagged malicious: 0.1.0, 0.2.0. Treat any of these as compromised.

How do I remediate md5-en if I installed it?

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

If md5-en was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is md5-en part of a known attack campaign?

Yes — md5-en is associated with the RLMA-2025-05621, 2025-10-md5-en, RLUA-2026-00505 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 md5-en across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for md5-en (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging md5-en across your stack and pipelines.

Malicious package

md5-enPyPI

Malicious code in md5-en (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191649

Immediate action

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

pip uninstall md5-en

What this malware does

Code downloads and starts an executable widely recognized as malware, then sends some results to a Telegram webhook.

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

Campaign: 2025-10-md5-en

Reasons (based on the campaign):

malware
Downloads and executes a remote executable.
obfuscation

Malicious versions

2 flagged

0.1.00.2.0

Indicators of compromise (SHA-256)

96ff96a78d323397493c43cc1c7e74aae0b698237a44c0db7794dd9da89bca1c

5c5f8392ba7d0abbe13ff70f46a7f112ba0ef16f6068faba47aff0c610b5d89d

1c7608df27812e170abf1fa650287b87174700cd5a23658ae8d81317f7cd93dc

62d127c876b3f452a6f8c85e005fa4d64007a81f96ae4bc56643835ff08e375d

d14d553efe50d24656274ed4b92c19da853a0edc4098c4734c3409857777cbb0

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for md5-en (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging md5-en across your stack and pipelines.
If you installed it — respond
md5-en 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 md5-en was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks md5-en before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. md5-en on PyPI has been identified as a malicious package (versions 0.1.0, 0.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-056212025-10-md5-enRLUA-2026-00505

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks md5-en-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