How do I remediate ldhpgemrdhs60152 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhpgemrdhs60152 (22 malicious versions).

Malicious package

ldhpgemrdhs60152npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs60152 is a confirmed malicious npm package (MAL-2025-48719) that executes malicious code on install (malicious versions 1.250915.11002, 1.250915.11348, 1.250915.11350…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs60152 (npm)

MAL-2025-48719

Immediate action

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

npm uninstall ldhpgemrdhs60152

What this malware does

The package ldhpgemrdhs60152 was found to contain malicious code.

Malicious versions

22 flagged

1.250915.110021.250915.113481.250915.113501.250915.115131.250915.115141.250915.118301.250916.107561.250916.114291.250917.108001.250917.114181.250918.108261.250918.113261.250918.113431.250918.115551.250918.118141.250923.108511.250923.110331.250926.114141.251021.107551.251021.115161.251021.115201.251022.11336

Indicators of compromise (SHA-256)

71cdba467fa78300a0acfab6610e80b534dab256552b051bb43b0edc1b810888

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ldhpgemrdhs60152 (22 malicious versions).
If you installed it — respond
Remove ldhpgemrdhs60152 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 ldhpgemrdhs60152 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. ldhpgemrdhs60152 on npm has been identified as a malicious package (versions 1.250915.11002, 1.250915.11348, 1.250915.11350, 1.250915.11513, 1.250915.11514, 1.250915.11830, 1.250916.10756, 1.250916.11429, and 14 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05848

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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