MAL-2026-14479 Malicious code in vite-plugin-bug-tracker (npm)
Malicious package
Published
MAL-2026-14479 is a malicious package: vite-plugin-bug-tracker (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-14479/ (Markdown: https://insights.sbomify.com/MAL-2026-14479/index.md)
- Package
- vite-plugin-bug-tracker
- Registry
- npm
What is MAL-2026-14479?
MAL-2026-14479 is a malicious package in vite-plugin-bug-tracker, published on 25 Aug 2026.
Official description
The package presents itself as a Vite bug-tracker plugin. Its transformIndexHtml hook injects an inline script into every built HTML page produced by the developer's Vite build. At runtime in the end user's browser, that injected script reads personally identifiable information from sessionStorage (account/username, phone number, real name via fields such as i.phone and i.realName) and transmits it via fetch (mode: 'no-cors'), sendBeacon, or an Image request. The destination URL is not written in cleartext: it is assembled at runtime by base64-decoding a bundled string and XOR-ing each byte with 42 (atob(_c).split('').map(c => String.fromCharCode(c.charCodeAt(0) ^ 42)).join('')). The exfiltration query string is likewise XOR+base64 encoded before being appended. The plugin also monkey-patches sessionStorage.setItem so that any write matching the configured scope triggers immediate exfiltration. As a result, applications built with this plugin ship a PII harvester to their production users whose reporting endpoint cannot be identified by inspecting the built bundle or a browser network trace at a glance.
What should I do about MAL-2026-14479?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.