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

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

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

@wizloft/harness-validation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @wizloft/harness-validation — how do I know if it already compromised me?

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

Yes — @wizloft/harness-validation is associated with the IN-MAL-2026-018410 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-validation 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-validation (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-validation across your stack and pipelines.

Malicious package

@wizloft/harness-validationnpm

@wizloft/harness-validation is a confirmed malicious npm package (MAL-2026-14289) that steals credentials and exfiltrates sensitive data (malicious version 0.1.1-alpha.3). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-14289

Immediate action

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

npm uninstall @wizloft/harness-validation

What this malware does

dist/index.js appends a heavily obfuscated obfuscator.io-style payload (string array _0x240a of length 303, decoder _0x4963, string-array rotation) after the clean TypeScript-compiled validation code. None of this obfuscated code is declared in dist/index.d.ts and it executes at top level on import '@wizloft/harness-validation'. Decoded string fragments include Ethereum RPC / block-explorer hostnames (h.drpc.org, pc.io/eth, stapi.io), a hardcoded attacker Ethereum address (0xa322E5f3...), Etherscan-style query parameters (?module=account, filterby=from), a spoofed browser User-Agent, and application/json / content-encoding request framing. The payload queries the block explorer for transactions from the hardcoded wallet, extracts a URL/payload from the transaction data, then fetches and executes the resolved content — a blockchain-based dead-drop that lets the publisher rotate the delivered code by posting a new transaction from that wallet, giving them a persistent mutable remote-code channel against every process that imports the library. Sibling packages in the @wizloft/* namespace (@wizloft/harness-evidence, @wizloft/harness-kernel) are declared dependencies at matching alpha versions and exhibit the same trojanized-library shape.

Malicious versions

1 flagged

0.1.1-alpha.3

Indicators of compromise (SHA-256)

67b0fc0f25eb3d7852b52d7e7db50071ac08ddfb1965df306bbf87ebf295cbe1

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @wizloft/harness-validation (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-validation across your stack and pipelines.
If you installed it — respond
@wizloft/harness-validation is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @wizloft/harness-validation 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-validation 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-validation 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-018410

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @wizloft/harness-validation-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database