Which versions of hydration-dim-ui are malicious?

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

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

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

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

Yes — hydration-dim-ui is associated with the IN-MAL-2026-018638 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-dim-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-dim-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-dim-ui across your stack and pipelines.

Malicious package

hydration-dim-uinpm

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

MAL-2026-14430

Immediate action

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

npm uninstall hydration-dim-ui

What this malware does

[email protected] presents itself as a calendar-day math utility, but its main entry dist/index.mjs runs at import time: it chmod 0755's dist/internal/math-calc.dat and spawns it detached. math-calc.dat is a Linux x86_64 ELF implant (self-labeled 'RedShell' / 'SECURE_BEACON') that connects to hardcoded C2 217.60.77.63 to provide an interactive reverse shell, bulk file exfiltration via 'POST /api/extract-receive HTTP/1.1' framed with BIGEXTRACT_START/FILE/BIGEXTRACT_END markers, SOCKS5 proxying, and port forwarding. The implant contains built-in commands to harvest SSH keys, credentials, and clipboard contents, and a stager path that curls additional ELF or shellcode blobs from http://217.60.77.63/Others/<name> and /SC/<name>, chmod +x's them, and executes them (including a memfd_create-based fileless variant via python3 syscall(319)). A /redshell persist command writes ~/.config/systemd/user/svc-update.service (Description='System Update Service', Restart=always) and enables it via systemctl --user, giving the RAT reboot-persistent execution under a deceptive service name. The JS surface is cover: daymath.mjs is pure JS with a no-op _ensureEngine() stub, the ELF provides no math and is never called from JS, index.mjs frames the binary as a 'native math accelerator' with SHA-256 integrity theatre, and README refers to a mismatched filename ('calc-cache.bin' vs actual 'math-calc.dat') to obscure the ELF. The package is documented to be pulled transitively via svelte-dim-ui, so a single install/import chain drops a fully functional backdoor on the installer's host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

16cd04f35f684a64b6abd8178154fc7d1f5a970c76f7d77c45635c1c3bcf0d9b

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-dim-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-dim-ui across your stack and pipelines.
If you installed it — respond
hydration-dim-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-dim-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-dim-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-dim-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-018638

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hydration-dim-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