How do I remediate dhpgemrdhs95005 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs95005 (21 malicious versions).

Malicious package

dhpgemrdhs95005npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs95005 is a confirmed malicious npm package (MAL-2025-48669) that executes malicious code on install (malicious versions 1.250729.11824, 1.250730.12055, 1.250730.12126…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs95005 (npm)

MAL-2025-48669

Immediate action

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

npm uninstall dhpgemrdhs95005

What this malware does

The package dhpgemrdhs95005 was found to contain malicious code.

Malicious versions

21 flagged

1.250729.118241.250730.120551.250730.121261.250730.121331.250731.107421.250804.111501.250804.117071.250812.108051.250815.107551.250815.108011.250815.108161.250815.108261.250816.117021.250820.120171.250821.110441.250910.118211.250917.115211.250917.118521.250918.110451.250923.118491.251009.11947

Indicators of compromise (SHA-256)

25032f9104498e1402df9fcf63cb13eed35f77804c529f87417fea348ac7d3c9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs95005 (21 malicious versions).
If you installed it — respond
Remove dhpgemrdhs95005 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 dhpgemrdhs95005 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. dhpgemrdhs95005 on npm has been identified as a malicious package (versions 1.250729.11824, 1.250730.12055, 1.250730.12126, 1.250730.12133, 1.250731.10742, 1.250804.11150, 1.250804.11707, 1.250812.10805, and 13 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05762

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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