How do I remediate ldhemrdhs51214 if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhemrdhs51214 (6 malicious versions).

Malicious package

ldhemrdhs51214npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs51214 is a confirmed malicious npm package (MAL-2025-48699) that executes malicious code on install (malicious versions 1.250921.10039, 1.250923.10850, 1.250923.11029…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs51214 (npm)

MAL-2025-48699

Immediate action

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

npm uninstall ldhemrdhs51214

What this malware does

The package ldhemrdhs51214 was found to contain malicious code.

Malicious versions

6 flagged

1.250921.100391.250923.108501.250923.110291.250923.110301.250923.110311.250926.11412

Indicators of compromise (SHA-256)

3cbbf5e216c12add725038d81f2f5f6bc45b7aea93ba1cc2e43580c75469859d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05828

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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