Which versions of hachutis are malicious?

The following npm versions of hachutis are flagged malicious: 1.0.0, 1.0.6. Treat any of these as compromised.

How do I remediate hachutis if I installed it?

Remove hachutis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hachutis — how do I know if it already compromised me?

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

Yes — hachutis is associated with the IN-MAL-2026-020458, IN-MAL-2026-020459 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 hachutis 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 hachutis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hachutis across your stack and pipelines.

Malicious package

hachutisnpm

hachutis is a confirmed malicious npm package (MAL-2026-16464) that executes malicious code on install (malicious versions 1.0.0, 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hachutis (npm)

MAL-2026-16464

Immediate action

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

npm uninstall hachutis

What this malware does

The tarball ships three undeclared prebuilt executables under bin/ (bin/cli, bin/cli-linux-amd64, and an 81 MB Bun-compiled bin/cli-http-linux) that are not exposed via package.json.bin. The manifest's only bin entry hatcher-env points to bin/cli.js, which is absent from the tarball, and the declared main src/index.js is an unrelated dotenv-style parser hardcoded to /home/hatch/test.dat with no reference to the shipped binaries. The bundled JS region of bin/cli-http-linux embeds the anonymous Cloudflare Tunnel host already-query-bacteria-agreed.trycloudflare.com adjacent to HTTP POST verbs, and the README instructs the installer to execute one of the./bin/ binaries at least once to 'activate the package in our systems.' Running the binary opens a channel from the installer's host to an attacker-controlled trycloudflare.com tunnel; the readable JS surface is a decoy for opaque native payloads whose actual behavior is not documented.

Malicious versions

2 flagged

1.0.01.0.6

Indicators of compromise (SHA-256)

455f1d04545c9ed17722705fe61415d7e536e2800c2a3c588ab69985004c73b9

8bf0269b9f1d010329c2005ab1908b3ac9952eae4302f8e08e6a52c848143152

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hachutis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hachutis across your stack and pipelines.
If you installed it — respond
Remove hachutis from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hachutis 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 hachutis 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. hachutis on npm has been identified as a malicious package (versions 1.0.0, 1.0.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020458IN-MAL-2026-020459

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hachutis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database