@wizloft/harness (npm) · Malicious Code
Affects @wizloft/harnessSource GCVE Database
Malicious package : remove @wizloft/harness and rotate any secrets on hosts that installed it.
Data as of 26 Oct 2026, 16:18 UTC
Malicious package
Published to npm · OSV MAL-2026-14285
What to do
Remove @wizloft/harness from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@wizloft/harness | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package @wizloft/harness version 0.1.1-alpha.3 contains malicious code that performs on-chain command and control (C2) operations. Upon import, it queries a public Ethereum smart contract to retrieve a payload string, which is then executed via eval() in the Node.js process, enabling arbitrary remote code execution. The malicious payload is obfuscated and stored on-chain, making it resistant to takedown and invisible to standard registry scanners. This behavior contradicts the package README's claim of having no executable binary.