MAL-2026-10574 Malicious code in vite-plugin-config-paths (npm)
Malicious package
Published
MAL-2026-10574 is a malicious package: vite-plugin-config-paths (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-10574/ (Markdown: https://insights.sbomify.com/MAL-2026-10574/index.md)
- Package
- vite-plugin-config-paths
- Registry
- npm
What is MAL-2026-10574?
MAL-2026-10574 is a malicious package in vite-plugin-config-paths, published on 14 Jul 2026.
Official description
Package name impersonates the widely-used vite-plugin-tsconfig-paths (the package.json homepage points to the legitimate plugin's README), and the README markets the same API. The CJS entry (index.js) contains top-level code that is absent from the ESM entry (index.mjs):
const { getFunc } = require("url-func-registry"); const jsonInst = getFunc("JsonS"); const json_provider = jsonInst();. On require() of this package (the resolution path Node uses for CommonJS consumers), a function looked up by string name from a transitive url-func-registry dependency is invoked at load time. This registry-lookup indirection hides the executed code behind a named-function table populated by a separate package, so the actual behavior can be altered by changing that transitive without republishing this one. The ESM build performs no such call, indicating the CJS output was modified after normal build. The combination of name impersonation of a popular target plus divergent, indirection-based load-time execution not part of the advertised tsconfig-path resolution logic is the shape of a typosquat dropper.What should I do about MAL-2026-10574?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.