How do I remediate ldhemrdhs92011 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs92011npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs92011 is a confirmed malicious npm package (MAL-2025-48711) that executes malicious code on install (malicious versions 1.250920.11449, 1.250920.11527, 1.250920.11533…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs92011 (npm)

MAL-2025-48711

Immediate action

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

npm uninstall ldhemrdhs92011

What this malware does

The package ldhemrdhs92011 was found to contain malicious code.

Malicious versions

6 flagged

1.250920.114491.250920.115271.250920.115331.250922.111371.250923.110391.250926.11420

Indicators of compromise (SHA-256)

1507cd13461a5aceb6b8fde5502209286a518167d6dd1c7a851ae3d63aa3f355

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05840

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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