How do I remediate dhemrdhs94010 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs94010 (10 malicious versions).

Malicious package

dhemrdhs94010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs94010 is a confirmed malicious npm package (MAL-2025-48642) that executes malicious code on install (malicious versions 1.250909.11838, 1.250910.11449, 1.250910.11553…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs94010 (npm)

MAL-2025-48642

Immediate action

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

npm uninstall dhemrdhs94010

What this malware does

The package dhemrdhs94010 was found to contain malicious code.

Malicious versions

10 flagged

1.250909.118381.250910.114491.250910.115531.250910.118381.250912.109301.250914.110561.250917.115181.250917.119191.250922.118251.250924.11132

Indicators of compromise (SHA-256)

d100f8296ff0925c79d14b6f90c45b312f380f30f291a96ca93e3ae9a0482eb9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs94010 (10 malicious versions).
If you installed it — respond
Remove dhemrdhs94010 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 dhemrdhs94010 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. dhemrdhs94010 on npm has been identified as a malicious package (versions 1.250909.11838, 1.250910.11449, 1.250910.11553, 1.250910.11838, 1.250912.10930, 1.250914.11056, 1.250917.11518, 1.250917.11919, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05739

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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