Which versions of hydration-ui-pkg are malicious?

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

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

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

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

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

Malicious package

hydration-ui-pkgnpm

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

MAL-2026-15900

Immediate action

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

npm uninstall hydration-ui-pkg

What this malware does

Package main (dist/index.mjs) locates dist/internal/mathcalc.mjs — a raw x86_64 ELF binary shipped under an.mjs extension and described in the README as a 'native math accelerator' — chmods it to 0755, verifies a pinned SHA-256, and spawns it detached via child_process.spawn on any require/import of the package. daymath.mjs contains a stub function with a comment stating it exists to make the math functions 'look like they rely on the binary', confirming the cover story. The ELF is a full remote-access implant (REDSHELL/SECURE_BEACON) that beacons to hardcoded C2 IP 217.60.77.63 and exfiltrates to https://litterbox.catbox.moe/resources/internals/api.php. Operator commands include /ssh_keys, /creds, /dbfind, /download and /dataextract for harvesting installer SSH private keys, credentials and databases, streamed chunked to POST /api/extract-receive. /redshell elf and /redshell bin fetch additional ELFs and shellcode over TLS-disabled HTTP into memfd (memfd_create syscall 319) or /tmp/.elf_XXXXXX and /tmp/.sc_XXXXXX for in-memory execution. /redshell persist writes ~/.config/systemd/user/svc-update.service (Description=System Update Service, Restart=always) and enables it via systemctl --user for login persistence. Extension-mismatched ELF, fake dependency stub, cover-story README, and hardcoded non-first-party C2 confirm intentional trojanization.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

d848dd11c0e0692f1f47c8fcb3cb0506316e96ab32f8b63a8913ad67e9570318

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hydration-ui-pkg-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