tailwind-form-stylesnpm
tailwind-form-styles is a confirmed malicious npm package (MAL-2026-16405) that steals credentials and exfiltrates sensitive data (malicious version 0.5.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tailwind-form-styles (npm)
What this malware does
The package presents itself as a Tailwind CSS forms plugin but its main entry src/index.js is heavily obfuscated (obfuscator.io-style rotated string array of 303 entries, hex-named identifiers, control-flow flattening) and has no relationship to the legitimate tailwindlabs/tailwindcss-forms project it mimics. On require()/import — which occurs whenever a consumer loads the plugin from tailwind.config — the module imports node:http, node:https, node:zlib and spawn from node:child_process, and installs global['r']=require and global['m']=module to stage further execution. It then issues HTTP requests to endpoints reconstructed from string-array fragments: an Etherscan-style transaction-list indexer and multiple Ethereum RPC hosts (drpc.org, publicnode, blockscout). A hardcoded Ethereum address 0xa322E5f39aDC2490EfD311D3080e6f0121063e1a is reassembled from fragments and used as the SENDER filter in eth_blockNumber, eth_getBlockByNumber, eth_getTransactionCount calls and in the txlist URL, and custom X-Payload-* headers gate later stages. The combination of Tailwind-plugin cover, obfuscated destination reconstruction, import-time network I/O to attacker-controlled infrastructure, child_process availability, and Ethereum on-chain command-and-control is the shape of a wallet-drainer / RCE stager, not a CSS plugin.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-form-styles (version 0.5.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-form-styles across your stack and pipelines.
If you installed it — respond
tailwind-form-styles is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwind-form-styles was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks tailwind-form-styles before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks tailwind-form-styles-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.