Which versions of ldhemrdhs92010 are malicious?

The following npm versions of ldhemrdhs92010 are flagged malicious: 1.250921.10059, 1.250923.11038, 1.250926.11420. Treat any of these as compromised.

How do I remediate ldhemrdhs92010 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs92010npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs92010 is a confirmed malicious npm package (MAL-2025-48710) that executes malicious code on install (malicious versions 1.250921.10059, 1.250923.11038, 1.250926.11420). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs92010 (npm)

MAL-2025-48710

Immediate action

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

npm uninstall ldhemrdhs92010

What this malware does

The package ldhemrdhs92010 was found to contain malicious code.

Malicious versions

3 flagged

1.250921.100591.250923.110381.250926.11420

Indicators of compromise (SHA-256)

ba85da8925e902b2883244ec91481301da11ec1182c404614c9659f35642f27b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05839

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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