Which versions of ldhemrdhs92009 are malicious?

The following npm versions of ldhemrdhs92009 are flagged malicious: 1.250920.11031, 1.250923.11038, 1.250926.11419. Treat any of these as compromised.

How do I remediate ldhemrdhs92009 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs92009npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs92009 is a confirmed malicious npm package (MAL-2025-48709) that executes malicious code on install (malicious versions 1.250920.11031, 1.250923.11038, 1.250926.11419). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs92009 (npm)

MAL-2025-48709

Immediate action

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

npm uninstall ldhemrdhs92009

What this malware does

The package ldhemrdhs92009 was found to contain malicious code.

Malicious versions

3 flagged

1.250920.110311.250923.110381.250926.11419

Indicators of compromise (SHA-256)

b25fd7bfcf444a0b66c7677657850767a72f2bc6d6512acacaf50f124b5c4688

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05838

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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