hydration-ui-clsnpm
Advisory published Updated
hydration-ui-cls is a confirmed malicious npm package (MAL-2026-14517) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in hydration-ui-cls (npm)
What this malware does
On import, dist/index.mjs runs a top-level async IIFE that chmods dist/internal/calc-eng.dat to 0755 and spawns it detached via child_process.spawn. The bundled 63KB Linux x86_64 ELF is a full remote-control implant: it beacons to a hardcoded C2 at 217.60.77.63 using a SECURE_BEACON/REDSHELL protocol, exposes interactive shell execution via /bin/sh and /bin/bash, and provides commands for SSH key enumeration (/ssh_keys), credential store harvest (/creds, /dbfind), bulk file exfiltration streamed as chunked POST /api/extract-receive to the C2, SOCKS5 proxy and TCP port-forwarding, in-memory ELF/shellcode staging via memfd with fetches from http://217.60.77.63/Others and /SC into /tmp/.elf_XXXXXX and /tmp/.sc_XXXXXX, and persistence via a user systemd unit named svc-update.service described as 'System Update Service' (with cron/bashrc/xdg alternatives). The binary is framed in code and README as a 'native math accelerator' performing a 'tiny startup self-check' with an SHA-256 integrity check and a 'Native accelerator loaded and verified.' log line, while the README claims no postinstall runs; the import-time spawn and RAT capability contradict that framing.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for hydration-ui-cls (version 1.0.0).
If you installed it — respond
hydration-ui-cls is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If hydration-ui-cls 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks hydration-ui-cls-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.