Malicious code in @wizloft/harness-kernel (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-14287
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (b6d73d94752604c9b48dd785c20cee875e268bb52c673bf3817f95000830fa85) 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. ## Source: ghsa-malware (130d79fc85d79e630b6be72735ac9378bcb31264f063b350e0bd392a9dff8fd3) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
- Source published
- 19 Aug 2026 08:33:41 UTC
- Source modified
- 23 Sep 2026 01:00:13 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.