How do I remediate dhpgemrdhs92092 if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhpgemrdhs92092 (14 malicious versions).

Malicious package

dhpgemrdhs92092npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhpgemrdhs92092 is a confirmed malicious npm package (MAL-2025-48666) that executes malicious code on install (malicious versions 1.250726.11900, 1.250727.11714, 1.250728.10936…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs92092 (npm)

MAL-2025-48666

Immediate action

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

npm uninstall dhpgemrdhs92092

What this malware does

The package dhpgemrdhs92092 was found to contain malicious code.

Malicious versions

14 flagged

1.250726.119001.250727.117141.250728.109361.250728.109431.250728.110231.250728.111061.250728.119371.250815.120291.250816.115091.250817.110131.250821.113421.250910.118391.250917.115021.250924.11150

Indicators of compromise (SHA-256)

97eaf99db9b6b979a0ad2fe6f537d0396c54b9de713da1abb2c677a63709420b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhpgemrdhs92092 (14 malicious versions).
If you installed it — respond
Remove dhpgemrdhs92092 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 dhpgemrdhs92092 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. dhpgemrdhs92092 on npm has been identified as a malicious package (versions 1.250726.11900, 1.250727.11714, 1.250728.10936, 1.250728.10943, 1.250728.11023, 1.250728.11106, 1.250728.11937, 1.250815.12029, and 6 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05759

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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