Which versions of ldhemrdhs92092 are malicious?

The following npm versions of ldhemrdhs92092 are flagged malicious: 1.250921.10105, 1.250923.11039, 1.250926.11421. Treat any of these as compromised.

How do I remediate ldhemrdhs92092 if I installed it?

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

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

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

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

Malicious package

ldhemrdhs92092npm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhemrdhs92092 is a confirmed malicious npm package (MAL-2025-48712) that executes malicious code on install (malicious versions 1.250921.10105, 1.250923.11039, 1.250926.11421). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs92092 (npm)

MAL-2025-48712

Immediate action

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

npm uninstall ldhemrdhs92092

What this malware does

The package ldhemrdhs92092 was found to contain malicious code.

Malicious versions

3 flagged

1.250921.101051.250923.110391.250926.11421

Indicators of compromise (SHA-256)

de9cfeed61e1e851e9687f4ffae092546bcc83d157e852f117be9565d3146aef

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05841

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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