Which versions of dim-hydration-ui are malicious?

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

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

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

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

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

Malicious package

dim-hydration-uinpm

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

MAL-2026-14429

Immediate action

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

npm uninstall dim-hydration-ui

What this malware does

The package is presented in its README as a set of day-math primitives, but dist/index.mjs runs a top-level async IIFE on import that chmod 0755's dist/internal/math.bin, verifies a hardcoded SHA-256, and cp.spawn's the ELF detached with stdio pipes. The shipped binary is not a math accelerator: strings inside dist/internal/math.bin identify it as a 'RedShell' remote-access implant with a command dispatcher exposing reverse-shell, /sysinfo, /ssh_keys, /creds, /dbfind, /clipboard, /env, /download, /upload, /dataextract, /shellcode, /memfd, SOCKS5 proxy, and port-forward capabilities. The implant beacons to a hardcoded C2 at 217.60.77.63, exfiltrates chunked file loot via HTTP POST /api/extract-receive, pulls follow-on payloads via curl over HTTP into memfd or /tmp with chmod +x, and installs user-level systemd persistence via svc-update.service. Simply importing the module launches a background process that gives a remote operator full shell, file, credential, and network control of the installer's host, with no advertised remote-access purpose and no user consent. The 'native math accelerator' naming and the SHA-256 integrity-pin framing serve as a cover story for the import-time C2 spawn.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3fefcd7c94e6eed5b5a69ce9ad5f4489c6532472ec604e6d15e5a96f63c59e51

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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