Which versions of ldhpgemrdhs51214 are malicious?

The following npm versions of ldhpgemrdhs51214 are flagged malicious: 1.250921.10040, 1.250923.10851, 1.250923.11032, 1.250926.11412. Treat any of these as compromised.

How do I remediate ldhpgemrdhs51214 if I installed it?

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

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

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

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

Malicious package

ldhpgemrdhs51214npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhpgemrdhs51214 is a confirmed malicious npm package (MAL-2025-48717) that executes malicious code on install (malicious versions 1.250921.10040, 1.250923.10851, 1.250923.11032…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhpgemrdhs51214 (npm)

MAL-2025-48717

Immediate action

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

npm uninstall ldhpgemrdhs51214

What this malware does

The package ldhpgemrdhs51214 was found to contain malicious code.

Malicious versions

4 flagged

1.250921.100401.250923.108511.250923.110321.250926.11412

Indicators of compromise (SHA-256)

75e92cbfc2e86631b544a998bde7b17fabd20f3b86199e3eae91560180d3f019

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05846

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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