How do I remediate ldhchukyso if I installed it?

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

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

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

Search your lockfiles and build artifacts for ldhchukyso (20 malicious versions).

Malicious package

ldhchukysonpm

Advisory published Oct 26, 2025Updated Dec 2, 2025

ldhchukyso is a confirmed malicious npm package (MAL-2025-48698) that executes malicious code on install (malicious versions 1.250722.11350, 1.250722.11354, 1.250722.11403…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ldhchukyso (npm)

MAL-2025-48698

Immediate action

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

npm uninstall ldhchukyso

What this malware does

The package ldhchukyso was found to contain malicious code.

Malicious versions

20 flagged

1.250722.113501.250722.113541.250722.114031.250722.114051.250722.114141.250722.114261.250722.114561.250722.114591.250722.118381.250722.118421.250722.118491.250722.119381.250723.111321.250723.111541.250801.109561.250801.110331.250801.114461.250801.117131.250801.117211.250819.11113

Indicators of compromise (SHA-256)

95e6118b312388fa5cbd82d471e664ccc36cd830b826a3f28c60b537d9a3f6c1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ldhchukyso (20 malicious versions).
If you installed it — respond
Remove ldhchukyso 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 ldhchukyso 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. ldhchukyso on npm has been identified as a malicious package (versions 1.250722.11350, 1.250722.11354, 1.250722.11403, 1.250722.11405, 1.250722.11414, 1.250722.11426, 1.250722.11456, 1.250722.11459, and 12 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05827

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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