Which versions of ldhpgemrdhs92011 are malicious?

The following npm versions of ldhpgemrdhs92011 are flagged malicious: 1.250920.11450, 1.250922.11137, 1.250923.11039, 1.250926.11421. Treat any of these as compromised.

How do I remediate ldhpgemrdhs92011 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhpgemrdhs92011 (4 malicious versions).

Malicious package

ldhpgemrdhs92011npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs92011 is a confirmed malicious npm package (MAL-2025-48729) that executes malicious code on install (malicious versions 1.250920.11450, 1.250922.11137, 1.250923.11039…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs92011 (npm)

MAL-2025-48729

Immediate action

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

npm uninstall ldhpgemrdhs92011

What this malware does

The package ldhpgemrdhs92011 was found to contain malicious code.

Malicious versions

4 flagged

1.250920.114501.250922.111371.250923.110391.250926.11421

Indicators of compromise (SHA-256)

59a8830b67b103857fc887a825d50d724bd43a71061d5b9f08606af93ef16fa3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05858

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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