Malicious code in @wizloft/harness (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-14285
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3679ede1e874f59f4be963544c3df43069cd335b2f888753b7411e42c7a5d3dd) dist/index.js — the package's main/exports entrypoint — presents ~200 lines of TypeScript-compiled SDK facade followed by a single ~40KB line of obfuscator.io output (303-entry rotated string array _0x240a with decoder _0x4963 and hex-identifier control-flow variables). Deobfuscation of the string table reveals hardcoded references to public Ethereum RPC endpoints (eth.drpc.org, 1rpc.io), an etherscan-style API query (?module=ac...), a hardcoded Ethereum contract address 0xa322E5f3..., a spoofed Mozilla/5.0 User-Agent, JSON POST machinery, and the sinks require, pipe, and eval. The composition matches the EtherHiding on-chain-C2 dropper pattern: on import, the code queries a smart contract via a public Ethereum RPC to retrieve an attacker-controlled next-stage payload string, then passes it to eval() in the consumer's Node process, yielding arbitrary remote code execution against the installer. The on-chain payload storage is mutable by the contract owner but immutable to registry takedown and invisible to standard registry scanners. The README's claim of 'no executable binary' contradicts the shipped dist/index.js. ## Source: ghsa-malware (7c45b346a08bc4c5f14a329f93f928988e7af1039d941528911a1a36080fdc9e) 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:21 UTC
- Source modified
- 23 Sep 2026 01:00:12 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.