How do I remediate dhemrdhs60015 if I installed it?

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

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

Yes — dhemrdhs60015 is associated with the RLMA-2025-05725 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 dhemrdhs60015 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dhemrdhs60015 (16 malicious versions).

Malicious package

dhemrdhs60015npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs60015 is a confirmed malicious npm package (MAL-2025-48627) that executes malicious code on install (malicious versions 1.250726.11850, 1.250726.11851, 1.250726.11852…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs60015 (npm)

MAL-2025-48627

Immediate action

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

npm uninstall dhemrdhs60015

What this malware does

The package dhemrdhs60015 was found to contain malicious code.

Malicious versions

16 flagged

1.250726.118501.250726.118511.250726.118521.250727.110581.250809.111141.250810.119371.250810.119401.250810.120161.250810.120271.250811.120561.250811.121051.250821.113421.250910.118491.250917.115221.250917.119201.250924.11155

Indicators of compromise (SHA-256)

44e8577259bb1b455558289ae6a8d84fceeddf7eab7b73adfe79da9fa1008f04

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs60015 (16 malicious versions).
If you installed it — respond
Remove dhemrdhs60015 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 dhemrdhs60015 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. dhemrdhs60015 on npm has been identified as a malicious package (versions 1.250726.11850, 1.250726.11851, 1.250726.11852, 1.250727.11058, 1.250809.11114, 1.250810.11937, 1.250810.11940, 1.250810.12016, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05725

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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