Which versions of ldhemrdhs92006 are malicious?

The following npm versions of ldhemrdhs92006 are flagged malicious: 1.250920.12347, 1.250923.11036, 1.250926.11418. Treat any of these as compromised.

How do I remediate ldhemrdhs92006 if I installed it?

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

If ldhemrdhs92006 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ldhemrdhs92006 part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ldhemrdhs92006 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhemrdhs92006 across your stack and pipelines.

Malicious package

ldhemrdhs92006npm

ldhemrdhs92006 is a confirmed malicious npm package (MAL-2025-48707) that executes malicious code on install (malicious versions 1.250920.12347, 1.250923.11036, 1.250926.11418). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs92006 (npm)

MAL-2025-48707

Immediate action

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

npm uninstall ldhemrdhs92006

What this malware does

The package ldhemrdhs92006 was found to contain malicious code.

Malicious versions

3 flagged

1.250920.123471.250923.110361.250926.11418

Indicators of compromise (SHA-256)

d7b0dd95127ff039237a4493fdd12f7c6ad9742c4e4ed32aba76521de695acbc

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ldhemrdhs92006 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhemrdhs92006 across your stack and pipelines.
If you installed it — respond
Remove ldhemrdhs92006 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 ldhemrdhs92006 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ldhemrdhs92006 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ldhemrdhs92006 on npm has been identified as a malicious package (versions 1.250920.12347, 1.250923.11036, 1.250926.11418 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05836

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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