Malicious code in @usemosaik/template-react-js (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-16047
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3174ac7cecbc1869ae5ac87ea585de744f6b7d17b8c089b746384c2b7e2355a3) This template package ships files/vite.config.js which, after a benign Vite header, appends ~26KB of heavily obfuscated code (obfuscator.io-style string-array with rotation dispatcher, hex payloads XOR-decoded at runtime with key 0xA2, arithmetic-hidden numeric literals). When the scaffolded project is run via `vite` / `npm run dev`, the config executes a `run()` routine that queries Ethereum JSON-RPC endpoints (`eth_getBlockByNumber`, `eth_getTransactionCount`) against a hardcoded sender address to resolve a command-and-control IP hidden in on-chain transaction data, fetches an XOR-encrypted payload over HTTP, decrypts it, and passes it to both `eval(...)` and `spawn('node', ['-e', payload], {detached: true, stdio: 'ignore', windowsHide: true})`, yielding a hidden detached Node process on the developer's machine. The package's declared `main` (dist/index.js) is inert, so scanners inspecting only the entry point miss the payload; the obfuscation and EtherHiding indirection exist solely to conceal the remote-execution chain from static review. Execution fires the first time a developer runs the scaffolded project generated from this template, giving full RCE on the developer's host. ## Source: ghsa-malware (9cb614be24802762692ee3d58173981e3c20bdebe4fabd6846ab71671568d4ca) 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
- 8 Sep 2026 16:37:43 UTC
- Source modified
- 8 Sep 2026 19:30:05 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.