How do I remediate dhemrdhs92010 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs92010 (20 malicious versions).

Malicious package

dhemrdhs92010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs92010 is a confirmed malicious npm package (MAL-2025-48638) that executes malicious code on install (malicious versions 1.250726.11840, 1.250809.11454, 1.250809.11500…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs92010 (npm)

MAL-2025-48638

Immediate action

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

npm uninstall dhemrdhs92010

What this malware does

The package dhemrdhs92010 was found to contain malicious code.

Malicious versions

20 flagged

1.250726.118401.250809.114541.250809.115001.250809.116341.250809.116491.250809.117491.250809.117501.250810.111291.250810.120161.250810.120271.250813.113471.250815.120161.250817.110131.250817.119231.250821.108551.250821.113421.250910.118431.250917.115181.250917.119201.250924.11150

Indicators of compromise (SHA-256)

5ceb23a609348bc49f8355c0fb5aa8ad822c332fec8bd20fad9e871fb5f7b264

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs92010 (20 malicious versions).
If you installed it — respond
Remove dhemrdhs92010 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 dhemrdhs92010 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. dhemrdhs92010 on npm has been identified as a malicious package (versions 1.250726.11840, 1.250809.11454, 1.250809.11500, 1.250809.11634, 1.250809.11649, 1.250809.11749, 1.250809.11750, 1.250810.11129, and 12 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05735

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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