Malicious code in vite-svg-config (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-14140
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (38e61dd39d0c1d39a3b80b7138582b334480c2fb89e990a2b64e6c59050a998f) The package's exported getPlugin/setPlugin functions decode two base64 constants (svgValidateKey, svgValidatePattern) at runtime. svgValidateKey decodes to the shell command `npm install node-internal-svg-loader --no-save --silent --no-audit --no-fund`, which is spawned with stdio:'ignore', windowsHide:true, and shell:true on Windows. svgValidatePattern decodes to the package name `node-internal-svg-loader`, which is then dynamically required and whose getPlugin() export is invoked. The command and target package name are both hidden behind base64 constants and misleading identifiers framed as SVG validation. Silencing flags (--silent, --no-audit, --no-fund, windowsHide) suppress user-visible output of the install. The result is that any consumer calling the package's advertised plugin API pulls and executes a separate npm package, whose contents are controlled by whoever owns that name, on the caller's machine.
- Source published
- 18 Aug 2026 22:47:03 UTC
- Source modified
- 18 Aug 2026 23:15:11 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.