How do I remediate dhpgemrdhs60152 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs60152 (11 malicious versions).

Malicious package

dhpgemrdhs60152npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs60152 is a confirmed malicious npm package (MAL-2025-48654) that executes malicious code on install (malicious versions 1.250726.11906, 1.250727.11613, 1.250809.11114…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs60152 (npm)

MAL-2025-48654

Immediate action

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

npm uninstall dhpgemrdhs60152

What this malware does

The package dhpgemrdhs60152 was found to contain malicious code.

Malicious versions

11 flagged

1.250726.119061.250727.116131.250809.111141.250810.120271.250816.107491.250816.108201.250821.109461.250910.118481.250916.109241.250917.115221.250924.11126

Indicators of compromise (SHA-256)

77ea3f7b8a28b886669589ef33b606867c9c180c9ee40297f6a40d70d04265dc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs60152 (11 malicious versions).
If you installed it — respond
Remove dhpgemrdhs60152 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 dhpgemrdhs60152 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. dhpgemrdhs60152 on npm has been identified as a malicious package (versions 1.250726.11906, 1.250727.11613, 1.250809.11114, 1.250810.12027, 1.250816.10749, 1.250816.10820, 1.250821.10946, 1.250910.11848, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05748

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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