How do I remediate dhemrdhs79029 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhemrdhs79029 (10 malicious versions).

Malicious package

dhemrdhs79029npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhemrdhs79029 is a confirmed malicious npm package (MAL-2025-48630) that executes malicious code on install (malicious versions 1.250727.10942, 1.250727.10944, 1.250729.11113…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhemrdhs79029 (npm)

MAL-2025-48630

Immediate action

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

npm uninstall dhemrdhs79029

What this malware does

The package dhemrdhs79029 was found to contain malicious code.

Malicious versions

10 flagged

1.250727.109421.250727.109441.250729.111131.250821.113421.250910.118451.250917.115211.250917.119201.250924.111551.251006.114311.251009.11011

Indicators of compromise (SHA-256)

3d44d3fe7fc0139820f2826d581c6e0b7e234e49592cb015109d1eea0de72abd

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhemrdhs79029 (10 malicious versions).
If you installed it — respond
Remove dhemrdhs79029 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 dhemrdhs79029 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. dhemrdhs79029 on npm has been identified as a malicious package (versions 1.250727.10942, 1.250727.10944, 1.250729.11113, 1.250821.11342, 1.250910.11845, 1.250917.11521, 1.250917.11920, 1.250924.11155, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05728

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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