How do I remediate dhpgemrdhs92010 if I installed it?

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

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

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

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

Malicious package

dhpgemrdhs92010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs92010 is a confirmed malicious npm package (MAL-2025-48664) that executes malicious code on install (malicious versions 1.250726.11842, 1.250809.11454, 1.250809.11500…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs92010 (npm)

MAL-2025-48664

Immediate action

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

npm uninstall dhpgemrdhs92010

What this malware does

The package dhpgemrdhs92010 was found to contain malicious code.

Malicious versions

21 flagged

1.250726.118421.250809.114541.250809.115001.250809.116341.250809.116441.250809.116481.250809.116491.250809.117491.250809.117501.250810.111291.250810.120161.250810.120271.250813.113471.250815.120171.250817.110131.250817.119231.250821.108551.250821.113421.250910.118431.250917.115181.250924.11150

Indicators of compromise (SHA-256)

3c7555cedfb2e78c1157e5a564e3657d3fe3aad2acaced756e0336fca838009c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs92010 (21 malicious versions).
If you installed it — respond
Remove dhpgemrdhs92010 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 dhpgemrdhs92010 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. dhpgemrdhs92010 on npm has been identified as a malicious package (versions 1.250726.11842, 1.250809.11454, 1.250809.11500, 1.250809.11634, 1.250809.11644, 1.250809.11648, 1.250809.11649, 1.250809.11749, and 13 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05757

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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