How do I remediate dhpgemrdhs94010 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs94010 (9 malicious versions).

Malicious package

dhpgemrdhs94010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs94010 is a confirmed malicious npm package (MAL-2025-48668) that executes malicious code on install (malicious versions 1.250909.11838, 1.250910.11450, 1.250910.11554…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs94010 (npm)

MAL-2025-48668

Immediate action

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

npm uninstall dhpgemrdhs94010

What this malware does

The package dhpgemrdhs94010 was found to contain malicious code.

Malicious versions

9 flagged

1.250909.118381.250910.114501.250910.115541.250910.118381.250912.109311.250914.110561.250917.115181.250922.118251.250924.11133

Indicators of compromise (SHA-256)

6fd137712c28406725894fd096074f5500a6f2dc4305aa6c23e0a9efcdafd1a4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs94010 (9 malicious versions).
If you installed it — respond
Remove dhpgemrdhs94010 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 dhpgemrdhs94010 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. dhpgemrdhs94010 on npm has been identified as a malicious package (versions 1.250909.11838, 1.250910.11450, 1.250910.11554, 1.250910.11838, 1.250912.10931, 1.250914.11056, 1.250917.11518, 1.250922.11825, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05761

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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