Which versions of hydenmj are malicious?

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

How do I remediate hydenmj if I installed it?

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

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

Yes — hydenmj is associated with the RLMA-2025-04773, 2025-08-k7eel, RLUA-2026-00414 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 hydenmj 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 hydenmj (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hydenmj across your stack and pipelines.

Malicious package

hydenmjPyPI

Malicious code in hydenmj (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-47772

Immediate action

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

pip uninstall hydenmj

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)

fac965aeb880eb5b3c7b0ee77655663ca33afe623d1a5851b8f1717b9e7fda2b

0d2dc2792335c148b5266fc9095b59e55db92344794ecee9dd4fe788c642de8b

82524d59837163aa01cabc41d849e511e785a0c1f6a4a33ee3d257f22c7f0fbc

71c49c04ea8bfcc2727f699bfaa0c2dcb83b027487713d703cbf6abc6ec564aa

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 hydenmj (version 0.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hydenmj across your stack and pipelines.
If you installed it — respond
hydenmj 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 hydenmj 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 hydenmj 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. hydenmj 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-047732025-08-k7eelRLUA-2026-00414

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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