Which versions of ldhemrdhs83600 are malicious?

The following npm versions of ldhemrdhs83600 are flagged malicious: 1.250921.10006, 1.250921.11837, 1.250923.11035, 1.250926.11416. Treat any of these as compromised.

How do I remediate ldhemrdhs83600 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs83600npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs83600 is a confirmed malicious npm package (MAL-2025-48704) that executes malicious code on install (malicious versions 1.250921.10006, 1.250921.11837, 1.250923.11035…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs83600 (npm)

MAL-2025-48704

Immediate action

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

npm uninstall ldhemrdhs83600

What this malware does

The package ldhemrdhs83600 was found to contain malicious code.

Malicious versions

4 flagged

1.250921.100061.250921.118371.250923.110351.250926.11416

Indicators of compromise (SHA-256)

a044b3578cde495d7be785ac7c339cc2df55bb25320278ec5abccfed1810c7b2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05833

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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