How do I remediate dhchukyso if I installed it?

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

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

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

Search your lockfiles and build artifacts for dhchukyso (10 malicious versions).

Malicious package

dhchukysonpm

Advisory published Oct 26, 2025Updated Dec 2, 2025

dhchukyso is a confirmed malicious npm package (MAL-2025-48625) that executes malicious code on install (malicious versions 1.250722.11405, 1.250723.11153, 1.250729.11130…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhchukyso (npm)

MAL-2025-48625

Immediate action

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

npm uninstall dhchukyso

What this malware does

The package dhchukyso was found to contain malicious code.

Malicious versions

10 flagged

1.250722.114051.250723.111531.250729.111301.250729.117521.250730.111071.250819.111151.251003.108151.251003.109231.251004.116061.251017.11556

Indicators of compromise (SHA-256)

8436c0274ed452351b16eaadc7c8d9c21f6c25ed2853036db789858ab5a0a512

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for dhchukyso (10 malicious versions).
If you installed it — respond
Remove dhchukyso 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 dhchukyso 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. dhchukyso on npm has been identified as a malicious package (versions 1.250722.11405, 1.250723.11153, 1.250729.11130, 1.250729.11752, 1.250730.11107, 1.250819.11115, 1.251003.10815, 1.251003.10923, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05723

References

getsafety.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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