How do I remediate dhemrdhs92009 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs92009 (16 malicious versions).

Malicious package

dhemrdhs92009npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs92009 is a confirmed malicious npm package (MAL-2025-48637) that executes malicious code on install (malicious versions 1.250723.10755, 1.250723.11344, 1.250725.11100…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs92009 (npm)

MAL-2025-48637

Immediate action

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

npm uninstall dhemrdhs92009

What this malware does

The package dhemrdhs92009 was found to contain malicious code.

Malicious versions

16 flagged

1.250723.107551.250723.113441.250725.111001.250725.114591.250801.107521.250801.116371.250801.116441.250817.114421.250817.117271.250817.117471.250817.118101.250821.113431.250910.118241.250917.115211.250917.119191.250924.11150

Indicators of compromise (SHA-256)

e2c8b4233e753c63eaec8dae360df39ba5b2f827078b1a7f87f1bf1c4d0c2c59

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs92009 (16 malicious versions).
If you installed it — respond
Remove dhemrdhs92009 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 dhemrdhs92009 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. dhemrdhs92009 on npm has been identified as a malicious package (versions 1.250723.10755, 1.250723.11344, 1.250725.11100, 1.250725.11459, 1.250801.10752, 1.250801.11637, 1.250801.11644, 1.250817.11442, and 8 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05734

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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