How do I remediate dhpgemrdhs92006 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs92006 (19 malicious versions).

Malicious package

dhpgemrdhs92006npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs92006 is a confirmed malicious npm package (MAL-2025-48660) that executes malicious code on install (malicious versions 1.250722.11131, 1.250722.11150, 1.250723.11353…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs92006 (npm)

MAL-2025-48660

Immediate action

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

npm uninstall dhpgemrdhs92006

What this malware does

The package dhpgemrdhs92006 was found to contain malicious code.

Malicious versions

19 flagged

1.250722.111311.250722.111501.250723.113531.250723.114301.250723.114351.250723.114571.250724.111101.250724.111371.250724.113151.250724.113211.250724.113241.250724.113271.250724.113511.250724.114231.250806.108341.250821.113431.250910.118271.250917.115211.250924.11155

Indicators of compromise (SHA-256)

132e57688e9a72d553fc671aad92e4e2dfb846fd8453e97fc3675a5fdf2a7e85

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs92006 (19 malicious versions).
If you installed it — respond
Remove dhpgemrdhs92006 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 dhpgemrdhs92006 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. dhpgemrdhs92006 on npm has been identified as a malicious package (versions 1.250722.11131, 1.250722.11150, 1.250723.11353, 1.250723.11430, 1.250723.11435, 1.250723.11457, 1.250724.11110, 1.250724.11137, and 11 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05754

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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