MAL-2026-14037 Malicious code in tailwind-plugin-kit (npm)
Malicious package
Published
MAL-2026-14037 is a malicious package: tailwind-plugin-kit (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-14037/ (Markdown: https://insights.sbomify.com/MAL-2026-14037/index.md)
- Package
- tailwind-plugin-kit
- Registry
- npm
What is MAL-2026-14037?
MAL-2026-14037 is a malicious package in tailwind-plugin-kit, published on 14 Aug 2026.
Official description
The package presents itself as a Tailwind CSS plugin toolkit but its exported
getPlugin function performs an HTTPS request to a hardcoded bare-IP endpoint (31.97.137.157:45000/icons/109) and passes the response's data.credits field to new Function(...) with a full Node.js execution context (require, module, exports, process, Buffer, globalThis, Promise). Any project following the README instructions and registering the package as a Tailwind plugin (plugins: [toolkit]) triggers execution of arbitrary attacker-controlled JavaScript on the developer/build machine. The destination URL is assembled by concatenating separate protocol/domain/path fragments, and the file also contains an unused setDefaultModule referencing well-known CDN hostnames (cloudflare, fastly, akamai, cloudfront) as a decoy — the actual network destination is the bare IP, not any CDN. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a second-stage infostealer payload targeting browser credential stores and machine identifiers on the loaded host.What should I do about MAL-2026-14037?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.