How do I remediate dhpgemrdhs92009 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs92009 (15 malicious versions).

Malicious package

dhpgemrdhs92009npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs92009 is a confirmed malicious npm package (MAL-2025-48663) that executes malicious code on install (malicious versions 1.250723.10755, 1.250723.11344, 1.250725.11100…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs92009 (npm)

MAL-2025-48663

Immediate action

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

npm uninstall dhpgemrdhs92009

What this malware does

The package dhpgemrdhs92009 was found to contain malicious code.

Malicious versions

15 flagged

1.250723.107551.250723.113441.250725.111001.250725.114591.250801.107531.250801.116371.250801.116441.250817.114431.250817.117271.250817.117481.250817.118101.250821.113431.250910.118241.250917.115211.250924.11150

Indicators of compromise (SHA-256)

4bf0c2c70a51e5ba0dfc3c90fe665f57003e8ef995f0b4c6634028e743509bc0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs92009 (15 malicious versions).
If you installed it — respond
Remove dhpgemrdhs92009 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 dhpgemrdhs92009 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. dhpgemrdhs92009 on npm has been identified as a malicious package (versions 1.250723.10755, 1.250723.11344, 1.250725.11100, 1.250725.11459, 1.250801.10753, 1.250801.11637, 1.250801.11644, 1.250817.11443, and 7 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05756

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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