Vulnerabilities

Vulnerability · MAL-2026-16282

Malicious code in tailwindcss-form (npm)

Published Sep 18, 2026 · catalog updated Oct 15, 2026 · Malicious code in tailwindcss-form

Open the advisory

Exploitation likelihood is not on this record for MAL-2026-16282. A missing EPSS score is not a low risk. Compare Malicious code in tailwindcss-form with the linked advisory before you change production.

Severity

Unknown—

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

Awaiting synchronization with FIRST

Remediation

Advisory link

Affected products

npm tailwindcss-form

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f5c6b39e2bde3263d10e2f20e707d06b981e746fda83ef7772233db33ae7a4f2) Package name mimics the legitimate tailwindcss-forms plugin (repo field points at tailwindlabs/tailwindcss-forms) but the main entry src/index.js is an obfuscator.io-packed bundle (303-entry rotated string array, control-flow flattening) whose top-level code has no relation to a Tailwind CSS plugin. On require() it loads node:http, node:https, node:zlib, and node:child_process, then issues requests to a set of hardcoded Ethereum endpoints (eth.blockscout.com, *.publicnode.com, *.drpc.org, 1rpc.io/eth) and an INDEXER_URL, carrying an etherscan-style txlist query against a hardcoded wallet address 0xa322E5f3... and custom x-payload-* headers. Response content is stashed into process globals (_t_u, _t_s, _H, _H2) that are then consumed by a child_process.spawn call, giving the operator of the indexer remote code execution on the installer's machine at import time. The combination of typosquatted name, obfuscator.io packing of the main entry, hardcoded remote endpoints acting as a command channel, and spawn of a fetched payload is a supply-chain trojan disguised as a Tailwind plugin. ## Source: ghsa-malware (a6360dfe9a149abb217abe22c0f48a3c37dffdc5b8ed3fb0e637a72cae6efbfc) 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.