Which versions of ldhpgemrdhs60015 are malicious?

The following npm versions of ldhpgemrdhs60015 are flagged malicious: 1.250922.11314, 1.250923.11032, 1.250926.11413. Treat any of these as compromised.

How do I remediate ldhpgemrdhs60015 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhpgemrdhs60015 (3 malicious versions).

Malicious package

ldhpgemrdhs60015npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs60015 is a confirmed malicious npm package (MAL-2025-48718) that executes malicious code on install (malicious versions 1.250922.11314, 1.250923.11032, 1.250926.11413). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs60015 (npm)

MAL-2025-48718

Immediate action

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

npm uninstall ldhpgemrdhs60015

What this malware does

The package ldhpgemrdhs60015 was found to contain malicious code.

Malicious versions

3 flagged

1.250922.113141.250923.110321.250926.11413

Indicators of compromise (SHA-256)

93367f3fe288cea7a741b74bb2fef022dd44e40941ebc4b365f26078560d2474

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ldhpgemrdhs60015 (3 malicious versions).
If you installed it — respond
Remove ldhpgemrdhs60015 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 ldhpgemrdhs60015 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. ldhpgemrdhs60015 on npm has been identified as a malicious package (versions 1.250922.11314, 1.250923.11032, 1.250926.11413 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05847

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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