Which versions of @wizloft/harness-kernel are malicious?

The following npm versions of @wizloft/harness-kernel are flagged malicious: 0.1.1-alpha.3. Treat any of these as compromised.

How do I remediate @wizloft/harness-kernel if I installed it?

@wizloft/harness-kernel 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 @wizloft/harness-kernel — how do I know if it already compromised me?

If @wizloft/harness-kernel 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 @wizloft/harness-kernel part of a known attack campaign?

Yes — @wizloft/harness-kernel is associated with the IN-MAL-2026-018411 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 @wizloft/harness-kernel 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 @wizloft/harness-kernel (version 0.1.1-alpha.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wizloft/harness-kernel across your stack and pipelines.

Malicious package

@wizloft/harness-kernelnpm

@wizloft/harness-kernel is a confirmed malicious npm package (MAL-2026-14287) that opens a backdoor for remote access (malicious version 0.1.1-alpha.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @wizloft/harness-kernel (npm)

MAL-2026-14287

Immediate action

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

npm uninstall @wizloft/harness-kernel

What this malware does

dist/index.js contains an obfuscated top-level async IIFE that executes on import. It queries Ethereum JSON-RPC endpoints (eth.drpc.org, eth.publicnode.com, ethereum-rpc.publicnode.com, and an Etherscan-like API) for the most recent transaction from a hardcoded marker address (0xa322E5f39aDC2490Ef6f0121063e358050D311D3080e), parses the transaction's to field into two IPv4 addresses, HTTP-fetches XOR-encrypted payloads from http://<ip>/0x/ls and http://<ip>:443/0x/cl, XOR-decrypts them, then executes the resulting JavaScript via eval(...) and a detached spawn('node', ['-e', <decrypted>], {detached:true}). The entire loader is packed with obfuscator.io-style transforms (hex _0x identifiers, rotating string array _0x240a, control-flow flattening) that conceal the network-fetch-and-exec chain behind benign-looking exports. On-chain C2 makes the exfil/RCE destination mutable and takedown-resistant; the payload contents are opaque and attacker-controlled.

Malicious versions

1 flagged

0.1.1-alpha.3

Indicators of compromise (SHA-256)

b6d73d94752604c9b48dd785c20cee875e268bb52c673bf3817f95000830fa85

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 @wizloft/harness-kernel (version 0.1.1-alpha.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @wizloft/harness-kernel across your stack and pipelines.
If you installed it — respond
@wizloft/harness-kernel 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 @wizloft/harness-kernel 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 @wizloft/harness-kernel 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. @wizloft/harness-kernel on npm has been identified as a malicious package (version 0.1.1-alpha.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018411

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wizloft/harness-kernel-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