vite-plugin-cleaner @4.1.3
Vulnerability report · Last retrieved from osv.dev August 7, 2026 at 2:10 AM UTC
OSV ID
MAL-2026-13463
Ecosystem
npm
Summary
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: amazon-inspector (35bc445ea196f979ad69189f4498586a09a51855b97e95dea02d01d197620237)
Protect your entire dependency tree
Scan your lock files automatically on every PR. Block malicious packages before they reach production.