# MAL-2026-13463: Malicious code in vite-plugin-cleaner (npm)


- **Type:** Malicious package
- **Package:** `vite-plugin-cleaner` (npm)
- **Published:** 6 Aug 2026
- **Also known as:** GHSA-rx9h-69c4-qhq5

## What is MAL-2026-13463?

MAL-2026-13463 is a malicious package in vite-plugin-cleaner, published on 6 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-13463?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-13463 is a malicious package: vite-plugin-cleaner (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-13463/ (Markdown: https://insights.sbomify.com/MAL-2026-13463/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-13463

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-13463/
Summaries are generated and may contain mistakes; the official description above is the record.