How do I remediate dhemrdhs92011 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs92011 (17 malicious versions).

Malicious package

dhemrdhs92011npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs92011 is a confirmed malicious npm package (MAL-2025-48639) that executes malicious code on install (malicious versions 1.250727.10943, 1.250730.10830, 1.250730.12043…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs92011 (npm)

MAL-2025-48639

Immediate action

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

npm uninstall dhemrdhs92011

What this malware does

The package dhemrdhs92011 was found to contain malicious code.

Malicious versions

17 flagged

1.250727.109431.250730.108301.250730.120431.250730.121241.250730.121301.250815.120291.250816.115121.250816.115161.250817.110121.250821.113421.250910.118401.250917.115181.250917.119201.250918.114411.250918.119381.250922.111381.250924.11150

Indicators of compromise (SHA-256)

eac5daccbac27bcba9516b50f1962727661aef92451afc1df1dd00ddede86aec

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs92011 (17 malicious versions).
If you installed it — respond
Remove dhemrdhs92011 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 dhemrdhs92011 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. dhemrdhs92011 on npm has been identified as a malicious package (versions 1.250727.10943, 1.250730.10830, 1.250730.12043, 1.250730.12124, 1.250730.12130, 1.250815.12029, 1.250816.11512, 1.250816.11516, and 9 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05736

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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