Which versions of hydration-dim-kit are malicious?

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

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

hydration-dim-kit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed hydration-dim-kit — how do I know if it already compromised me?

If hydration-dim-kit 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.

Is hydration-dim-kit part of a known attack campaign?

Yes — hydration-dim-kit is associated with the GHSA-p33f-w7x3-mxrr, IN-MAL-2026-018598 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-kit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hydration-dim-kit (version 1.0.0).

Malicious package

hydration-dim-kitnpm

Advisory published Aug 23, 2026Updated Aug 24, 2026

hydration-dim-kit is a confirmed malicious npm package (MAL-2026-14385) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hydration-dim-kit (npm)

MAL-2026-14385

Immediate action

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

npm uninstall hydration-dim-kit

What this malware does

On import, dist/index.mjs verifies a SHA-256 digest of a bundled Linux x86_64 ELF at dist/internal/calc.dat, chmods it to 0755, and spawns it detached with piped stdio from a top-level async IIFE. The binary is documented in the README as a 'native math accelerator', but its strings identify it as a REDSHELL remote-access implant that beacons to hardcoded C2 endpoint 217.60.77.63 using a 'SECURE_BEACON|...|REDSHELL' framing. The implant exposes a full remote-command menu including shell execution, SOCKS5 proxying, TCP port forwarding, ELF download and in-memory execution via memfd_create, shellcode download and execution, /ssh_keys, /creds, /dbfind, /clipboard, /env, /adduser, /enableuser, and a BIGEXTRACT chunked file-exfil streamer that POSTs octet-stream chunks to /api/extract-receive on the C2. For persistence, the implant writes ~/.config/systemd/user/svc-update.service (Description='System Update Service', ExecStart pointing at /proc/self/exe, Restart=always) and runs 'systemctl --user daemon-reload && systemctl --user enable --now svc-update.service' to survive reboot under a disguised name. Package name and stated purpose (calendar-day hydration math) are unrelated to the binary's actual capabilities; the 'calc.dat' filename and 'compiled math-core' framing are cover story.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

160a3dfc2bb67aac05d56a19d9b87ab7d75a6ae84dbe497cbffcc14cf0671983

3659ec02e8317602c089b822a4a0533bee515d9666d07fdaf3cdf8b315a46147

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for hydration-dim-kit (version 1.0.0).
If you installed it — respond
hydration-dim-kit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If hydration-dim-kit 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

No. hydration-dim-kit 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

GHSA-p33f-w7x3-mxrrIN-MAL-2026-018598

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hydration-dim-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database