Which versions of ldhemrdhs60214 are malicious?

The following npm versions of ldhemrdhs60214 are flagged malicious: 1.250921.10047, 1.250923.11033, 1.250926.11414. Treat any of these as compromised.

How do I remediate ldhemrdhs60214 if I installed it?

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

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

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

Malicious package

ldhemrdhs60214npm

ldhemrdhs60214 is a confirmed malicious npm package (MAL-2025-48702) that executes malicious code on install (malicious versions 1.250921.10047, 1.250923.11033, 1.250926.11414). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhemrdhs60214 (npm)

MAL-2025-48702

Immediate action

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

npm uninstall ldhemrdhs60214

What this malware does

The package ldhemrdhs60214 was found to contain malicious code.

Malicious versions

3 flagged

1.250921.100471.250923.110331.250926.11414

Indicators of compromise (SHA-256)

a6d47f6bd492901f320c18a34191296abf67de0c71831759fae3c3179c45bbd3

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

Campaign

RLMA-2025-05831

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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