How do I remediate ldhpgemrdhs95005 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhpgemrdhs95005 (17 malicious versions).

Malicious package

ldhpgemrdhs95005npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs95005 is a confirmed malicious npm package (MAL-2025-48733) that executes malicious code on install (malicious versions 1.250914.11444, 1.250914.11800, 1.250914.11809…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs95005 (npm)

MAL-2025-48733

Immediate action

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

npm uninstall ldhpgemrdhs95005

What this malware does

The package ldhpgemrdhs95005 was found to contain malicious code.

Malicious versions

17 flagged

1.250914.114441.250914.118001.250914.118091.250915.108491.250915.113471.250915.115141.250915.118291.250916.107561.250916.114291.250917.108001.250917.114181.250918.108261.250918.110281.250918.113411.250918.118131.250923.110411.250926.11423

Indicators of compromise (SHA-256)

cf94a0ace1c8db0627cd7c2a1b2902ac79a695edd68132208dc97d150f89522c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ldhpgemrdhs95005 (17 malicious versions).
If you installed it — respond
Remove ldhpgemrdhs95005 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 ldhpgemrdhs95005 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. ldhpgemrdhs95005 on npm has been identified as a malicious package (versions 1.250914.11444, 1.250914.11800, 1.250914.11809, 1.250915.10849, 1.250915.11347, 1.250915.11514, 1.250915.11829, 1.250916.10756, and 9 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05862

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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