MAL-2026-16262 Malicious code in tailwindcss-form-ui (npm)
Malicious package
Published
MAL-2026-16262 is a malicious package: tailwindcss-form-ui (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-16262/ (Markdown: https://insights.sbomify.com/MAL-2026-16262/index.md)
- Package
- tailwindcss-form-ui
- Registry
- npm
What is MAL-2026-16262?
MAL-2026-16262 is a malicious package in tailwindcss-form-ui, published on 17 Sep 2026.
Official description
Package name and repository field impersonate the legitimate tailwindlabs/tailwindcss-forms plugin, but the shipped main entry src/index.js is a fully obfuscated (obfuscator.io string-array) module that has nothing to do with Tailwind CSS. On module load it imports node:child_process (spawn), node:http/https, node:zlib and node:url, builds a list of Ethereum JSON-RPC endpoints (process.env.ETH_RPC_URL, *.publicnode.com, drpc.org, 1rpc.io/eth, blockscout) and an Etherscan-style txlist URL for the hardcoded sender address 0xa322E5f39aDC2490EfD311D3080e6f0121063e1a, and polls eth_blockNumber / eth_getBlockByNumber / eth_getTransactionCount to retrieve attacker-published transactions. The retrieved payloads are decompressed via gunzip/inflate/brotli and passed to child_process.spawn, giving whoever controls that Ethereum address arbitrary command execution on any host that requires or imports the package. The on-chain command channel is takedown-resistant. The Tailwind-forms identity, the obfuscated main, and the require-time RCE together form a cover-story typosquat delivering installer-side remote code execution.
What should I do about MAL-2026-16262?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.