How do I remediate dhpgemrdhs83600 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs83600 (7 malicious versions).

Malicious package

dhpgemrdhs83600npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

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

Malicious code in dhpgemrdhs83600 (npm)

MAL-2025-48657

Immediate action

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

npm uninstall dhpgemrdhs83600

What this malware does

The package dhpgemrdhs83600 was found to contain malicious code.

Malicious versions

7 flagged

1.250811.109081.250811.120571.250821.113431.250822.111421.250910.118351.250917.114131.250924.11155

Indicators of compromise (SHA-256)

a291d94ec1dd50c9c6d8ab13df7fdd18c536cf3e7b82c35432d2752977f9d8b0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05751

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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