Which versions of haodesk-ui are malicious?

The following npm versions of haodesk-ui are flagged malicious: 4.0.2. Treat any of these as compromised.

How do I remediate haodesk-ui if I installed it?

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

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

Yes — haodesk-ui is associated with the RLMA-2026-01341 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 haodesk-ui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for haodesk-ui (version 4.0.2).

Malicious package

haodesk-uinpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

haodesk-ui is a confirmed malicious npm package (MAL-2026-1743) that executes malicious code on install (malicious version 4.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in haodesk-ui (npm)

MAL-2026-1743

Immediate action

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

npm uninstall haodesk-ui

What this malware does

The package haodesk-ui was found to contain malicious code.

Malicious versions

1 flagged

4.0.2

Indicators of compromise (SHA-256)

87c47ddc093ed1405e09d234115b8c8045921f5db25f4559a97589bdd6b469f8

d84a56e7e332520633c65a2690e70d5eb4792907c98da8a7d6830a463438c7d2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for haodesk-ui (version 4.0.2).
If you installed it — respond
Remove haodesk-ui 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 haodesk-ui 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. haodesk-ui on npm has been identified as a malicious package (version 4.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01341

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks haodesk-ui-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