Vulnerability
Malicious code in vite-react-toolkit (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (879905a93676f42398cca583eb921d5ee04a7c84068d7aa0123a7cefdf26d995) On import/require of vite-react-toolkit, src/features/extras/config.js (reached via the package main → createConfig.js → features/plugins.js side-effect import chain) fetches https://www.jsonkeeper.com/b/AAON3 with axios, extracts the response's `.config` field, and passes it to `new Function('require', s)(require)` — executing attacker-controlled JavaScript in the installer's Node.js process with full module-loading capability via `createRequire(import.meta.url)`. The fetch retries 5 times and swallows errors silently; `console.log` is saved and restored around the call to suppress output from the injected code. The dropper URL is hidden behind a fake local `process.env` object whose keys are named `DEV_API_KEY`/`DEV_SECRET_KEY`/`DEV_SECRET_VALUE` to look like ordinary environment variable reads. The package advertises itself as a Vite configuration helper, which has no need for network I/O at import time. jsonkeeper.com is an anonymous, mutable paste host — the served bytes can change at any time without any change to the package — so the attacker controls what runs in every consumer's dev/build pipeline whenever this module is imported. ## Source: ghsa-malware (316e2881a83a38ed8663fab07132eae5000d17aa215009a96762f5ec381c1981) 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.
No CVSS base score from NVD or GHSA yet. NVD typically scores within 24–72 hours of publication; GHSA usually within a day for OSS-flagged CVEs. Last record update .
For interim severity, fall back on KEV / EXPLOIT signals and the EPSS percentile (lower panel). Re-check this CVE after one cron tick — the score lands automatically when the source publishes.
FIRST.org publishes EPSS daily. Coverage isn't universal — pre-disclosure CVEs and reserved IDs don't carry an EPSS score until at least one exploitation signal lands. Score will appear within 24 hours of the next EPSS pull.
No exploitation, limited impact or prevalence