Which versions of hydration-vli-ui are malicious?

The following npm versions of hydration-vli-ui are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hydration-vli-ui if I installed it?

hydration-vli-ui 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.

I already installed hydration-vli-ui — how do I know if it already compromised me?

If hydration-vli-ui 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.

Is hydration-vli-ui part of a known attack campaign?

Yes — hydration-vli-ui is associated with the IN-MAL-2026-018749 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 hydration-vli-ui across my projects, lockfiles, and CI pipelines?

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

Malicious package

hydration-vli-uinpm

hydration-vli-ui is a confirmed malicious npm package (MAL-2026-14535) 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-vli-ui (npm)

MAL-2026-14535

Immediate action

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

npm uninstall hydration-vli-ui

What this malware does

The package's main entry (dist/index.mjs) locates dist/internal/math.mjs, chmods it to 0755, and spawns it as a detached child process every time the package is imported. The file is not JavaScript: its bytes begin with the ELF magic and it is a Linux x86_64 executable, renamed with an.mjs extension and framed in the README as a 'native math accelerator' referring to a nonexistent 'calc-cache.bin' file. Strings inside the ELF describe a full remote-access implant with a hardcoded C2 at 217.60.77.63, a 'SECURE_BEACON' protocol, and '/redshell' command handlers for socks/portfwd tunneling, arbitrary file drop-and-exec, shellcode injection, memfd_create-based in-memory execution, and systemd user-unit persistence (svc-update.service). Received commands are dispatched into /bin/sh and /bin/bash on the installer's host. The implant also exposes '/dataextract' and '/download' commands that POST arbitrary file contents via chunked HTTP to '/api/extract-receive' on the C2 host, along with '/ssh_keys', '/creds', '/dbfind', '/clipboard', and '/env' commands that harvest the installer's SSH keys, credential files, database contents, clipboard, and environment variables. Reachability requires only 'import "hydration-vli-ui"' — no user action, no authentication on the beacon channel — giving the C2 operator full remote shell control of any machine that installs and loads the package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

44daff58b8bb4bd4dfad78141323781dc5972c3b5e5a4506834c2e69ff7d0480

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hydration-vli-ui (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hydration-vli-ui across your stack and pipelines.
If you installed it — respond
hydration-vli-ui 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-vli-ui 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.
How O3 protects you
O3 blocks hydration-vli-ui 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. hydration-vli-ui on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018749

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hydration-vli-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database