How do I remediate dhemrdhs84006 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs84006 (11 malicious versions).

Malicious package

dhemrdhs84006npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs84006 is a confirmed malicious npm package (MAL-2025-48632) that executes malicious code on install (malicious versions 1.250811.10855, 1.250811.12057, 1.250821.11342…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs84006 (npm)

MAL-2025-48632

Immediate action

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

npm uninstall dhemrdhs84006

What this malware does

The package dhemrdhs84006 was found to contain malicious code.

Malicious versions

11 flagged

1.250811.108551.250811.120571.250821.113421.250821.119171.250822.109441.250822.111411.250910.118341.250916.119491.250917.115021.250917.119191.250924.11155

Indicators of compromise (SHA-256)

6383e7078f71c2ab79b28fcaeb785fe820f3c81d315f2d64e8c8e3dcd8a7db1a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs84006 (11 malicious versions).
If you installed it — respond
Remove dhemrdhs84006 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 dhemrdhs84006 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. dhemrdhs84006 on npm has been identified as a malicious package (versions 1.250811.10855, 1.250811.12057, 1.250821.11342, 1.250821.11917, 1.250822.10944, 1.250822.11141, 1.250910.11834, 1.250916.11949, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05730

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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