Which versions of ldhemrdhs60015 are malicious?

The following npm versions of ldhemrdhs60015 are flagged malicious: 1.250922.11313, 1.250923.11032, 1.250926.11413. Treat any of these as compromised.

How do I remediate ldhemrdhs60015 if I installed it?

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

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

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

Malicious package

ldhemrdhs60015npm

ldhemrdhs60015 is a confirmed malicious npm package (MAL-2025-48700) that executes malicious code on install (malicious versions 1.250922.11313, 1.250923.11032, 1.250926.11413). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs60015 (npm)

MAL-2025-48700

Immediate action

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

npm uninstall ldhemrdhs60015

What this malware does

The package ldhemrdhs60015 was found to contain malicious code.

Malicious versions

3 flagged

1.250922.113131.250923.110321.250926.11413

Indicators of compromise (SHA-256)

444bc6a1716378bccd65ed31a23aa202ec6c960bd3905ee5fecadf8890dabef0

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

Campaign

RLMA-2025-05829

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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