Which versions of dhpgemrdhs51214 are malicious?

The following npm versions of dhpgemrdhs51214 are flagged malicious: 1.250823.11711, 1.250910.11851, 1.250917.11522, 1.250924.11156. Treat any of these as compromised.

How do I remediate dhpgemrdhs51214 if I installed it?

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

If dhpgemrdhs51214 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dhpgemrdhs51214 part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dhpgemrdhs51214 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dhpgemrdhs51214 across your stack and pipelines.

Malicious package

dhpgemrdhs51214npm

dhpgemrdhs51214 is a confirmed malicious npm package (MAL-2025-48652) that executes malicious code on install (malicious versions 1.250823.11711, 1.250910.11851, 1.250917.11522…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhpgemrdhs51214 (npm)

MAL-2025-48652

Immediate action

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

npm uninstall dhpgemrdhs51214

What this malware does

The package dhpgemrdhs51214 was found to contain malicious code.

Malicious versions

4 flagged

1.250823.117111.250910.118511.250917.115221.250924.11156

Indicators of compromise (SHA-256)

80f8f8f4950a6cb91c6f580f778ee2f608418926d105a5aefeb5e47060d0705b

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dhpgemrdhs51214 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dhpgemrdhs51214 across your stack and pipelines.
If you installed it — respond
Remove dhpgemrdhs51214 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 dhpgemrdhs51214 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dhpgemrdhs51214 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dhpgemrdhs51214 on npm has been identified as a malicious package (versions 1.250823.11711, 1.250910.11851, 1.250917.11522, 1.250924.11156 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05746

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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