How do I remediate dhemrdhs92006 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs92006 (14 malicious versions).

Malicious package

dhemrdhs92006npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs92006 is a confirmed malicious npm package (MAL-2025-48634) that executes malicious code on install (malicious versions 1.250722.11131, 1.250722.11150, 1.250723.11351…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs92006 (npm)

MAL-2025-48634

Immediate action

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

npm uninstall dhemrdhs92006

What this malware does

The package dhemrdhs92006 was found to contain malicious code.

Malicious versions

14 flagged

1.250722.111311.250722.111501.250723.113511.250723.114571.250724.111101.250724.111371.250724.113141.250806.108341.250821.113421.250910.118271.250910.118301.250917.115211.250917.119191.250924.11154

Indicators of compromise (SHA-256)

7ebc337468aef2c8760e4541066fe7a12d74504031b59dd148f6bad8bc625659

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs92006 (14 malicious versions).
If you installed it — respond
Remove dhemrdhs92006 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 dhemrdhs92006 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. dhemrdhs92006 on npm has been identified as a malicious package (versions 1.250722.11131, 1.250722.11150, 1.250723.11351, 1.250723.11457, 1.250724.11110, 1.250724.11137, 1.250724.11314, 1.250806.10834, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05732

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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