@wizloft/harness-plugin-repository-files

Details

**Severity:** Critical

**Affected versions:** `= 0.1.1-alpha.3`

## Source: amazon-inspector (d8197c156f5877fb7a024a3007bed2da30176f74960e3fa271cac4c4369f2705)
dist/index.js of @wizloft/harness-plugin-repository-files ships a small legitimate wizloft-harness repository-files plugin followed at line 209 by a ~35KB obfuscator.io-packed IIFE (303-entry rotated string array _0x240a with decoder _0x4963, control-flow flattening, hex-named identifiers). Decoded strings in the appended segment include Ethereum JSON-RPC and block-explorer endpoints (drpc.org, publicnode.com, blockscout, an etherscan-style txlist/account API), a hardcoded mixed-case ETH address prefix 0xa322E5f3..., a forged Chrome User-Agent, brotli/gzip decompression, AbortController-based fetch, and a custom /0x/ls exfil path with x-payload-* headers. The payload runs at module load whenever a consumer imports the package and has no relationship to the advertised purpose of reading repository files for a harness runtime. Only the trailing segment is obfuscated; the legitimate plugin portion is plain ESM, indicating a hostile payload smuggled onto an otherwise-clean plugin build.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/212ab477a3bdce7d9f5412f6647f735d6aecceb6/osv/malicious/npm/@wizloft/harness-plugin-repository-files/MAL-2026-14288.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/212ab477a3bdce7d9f5412f6647f735d6aecceb6/osv/malicious/npm/@wizloft/harness-plugin-repository-files/MAL-2026-14288.json
- https://www.npmjs.com/package/@wizloft/harness-plugin-repository-files/v/0.1.1-alpha.3
- https://github.com/advisories/GHSA-3m3c-jw57-r32v

Compromised versions (1)

• = 0.1.1-alpha.3

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.