Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ldhchukysonpm

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
  1. Find it

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

  2. 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.

  3. Did it already run?

    If ldhchukyso 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.

  4. How O3 protects you

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

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.

Explore

ldhchukyso (npm) malicious package — MAL-2025-48698 | O3 Security