Which versions of ldhemrdhs95005 are malicious?

The following npm versions of ldhemrdhs95005 are flagged malicious: 1.250914.11444, 1.250917.11921, 1.250923.11042, 1.250926.11423. Treat any of these as compromised.

How do I remediate ldhemrdhs95005 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs95005npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs95005 is a confirmed malicious npm package (MAL-2025-48715) that executes malicious code on install (malicious versions 1.250914.11444, 1.250917.11921, 1.250923.11042…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs95005 (npm)

MAL-2025-48715

Immediate action

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

npm uninstall ldhemrdhs95005

What this malware does

The package ldhemrdhs95005 was found to contain malicious code.

Malicious versions

4 flagged

1.250914.114441.250917.119211.250923.110421.250926.11423

Indicators of compromise (SHA-256)

a122c0707b32e997b94834f517880987cf1e6a21325fabda926daf29411f047e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05844

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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