Which versions of hatdhat-testkit are malicious?

The following npm versions of hatdhat-testkit are flagged malicious: 3.2.14. Treat any of these as compromised.

How do I remediate hatdhat-testkit if I installed it?

hatdhat-testkit 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 hatdhat-testkit — how do I know if it already compromised me?

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

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

Malicious package

hatdhat-testkitnpm

hatdhat-testkit is a confirmed malicious npm package (MAL-2026-14373) that opens a backdoor for remote access (malicious version 3.2.14). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hatdhat-testkit (npm)

MAL-2026-14373

Immediate action

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

npm uninstall hatdhat-testkit

What this malware does

Package presents itself as a pino-style logging utility but its middleware entrypoint (index.js) spawns lib/caller.js as a detached Node process. caller.js contains a fake process object whose env.DEV_API_KEY, env.DEV_SECRET_KEY, and env.DEV_SECRET_VALUE are base64 strings that decode to the URL https://api.jsonstorage.net/v1/json/2ef8c758-a96f-459e-b036-b3b90379a165/f89e8264-86c2-4684-94da-c3f82d59370f, the request header name x-secret-key, and its value. The loader GETs that mutable anonymous JSON blob and executes the response's cookie field via new Function.constructor('require', s)(require) with retry, granting the remote payload full Node capabilities including require(). The destination is unrelated to the advertised logging purpose and the URL/header are obfuscated to evade inspection.

Malicious versions

1 flagged

3.2.14

Indicators of compromise (SHA-256)

83b6e58e31221d5d14386a193ab49381950bb01307ac4fb4d7e5c30d246046d9

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hatdhat-testkit (version 3.2.14). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hatdhat-testkit across your stack and pipelines.
If you installed it — respond
hatdhat-testkit 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 hatdhat-testkit 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 hatdhat-testkit 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. hatdhat-testkit on npm has been identified as a malicious package (version 3.2.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018566

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hatdhat-testkit-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