How do I remediate dhemrdhs83600 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs83600 (9 malicious versions).

Malicious package

dhemrdhs83600npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

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

Malicious code in dhemrdhs83600 (npm)

MAL-2025-48631

Immediate action

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

npm uninstall dhemrdhs83600

What this malware does

The package dhemrdhs83600 was found to contain malicious code.

Malicious versions

9 flagged

1.250811.109081.250811.120571.250821.113421.250822.111421.250910.118351.250917.114131.250917.119191.250921.118331.250924.11155

Indicators of compromise (SHA-256)

cca0b3ccaea74d21726b13aa9d15b4bba2518bf1118dc641486d92d075d45f7f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs83600 (9 malicious versions).
If you installed it — respond
Remove dhemrdhs83600 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 dhemrdhs83600 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. dhemrdhs83600 on npm has been identified as a malicious package (versions 1.250811.10908, 1.250811.12057, 1.250821.11342, 1.250822.11142, 1.250910.11835, 1.250917.11413, 1.250917.11919, 1.250921.11833, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05729

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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