Which versions of ldhemrdhs95006 are malicious?

The following npm versions of ldhemrdhs95006 are flagged malicious: 1.250921.10116, 1.250923.11042, 1.250926.11424. Treat any of these as compromised.

How do I remediate ldhemrdhs95006 if I installed it?

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

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

Yes — ldhemrdhs95006 is associated with the RLMA-2025-05845 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 ldhemrdhs95006 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 ldhemrdhs95006 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhemrdhs95006 across your stack and pipelines.

Malicious package

ldhemrdhs95006npm

ldhemrdhs95006 is a confirmed malicious npm package (MAL-2025-48716) that executes malicious code on install (malicious versions 1.250921.10116, 1.250923.11042, 1.250926.11424). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs95006 (npm)

MAL-2025-48716

Immediate action

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

npm uninstall ldhemrdhs95006

What this malware does

The package ldhemrdhs95006 was found to contain malicious code.

Malicious versions

3 flagged

1.250921.101161.250923.110421.250926.11424

Indicators of compromise (SHA-256)

aa8da11875b3f6727b679e4a46b990967a9915f469b4d216f9bc623d8fcd8a7e

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 ldhemrdhs95006 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ldhemrdhs95006 across your stack and pipelines.
If you installed it — respond
Remove ldhemrdhs95006 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 ldhemrdhs95006 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 ldhemrdhs95006 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. ldhemrdhs95006 on npm has been identified as a malicious package (versions 1.250921.10116, 1.250923.11042, 1.250926.11424 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05845

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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