tailwindcss-forms-stylenpm
tailwindcss-forms-style is a confirmed malicious npm package (MAL-2026-15636) that opens a backdoor for remote access (malicious version 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in tailwindcss-forms-style (npm)
What this malware does
Package typosquats @tailwindcss/forms. On require('tailwindcss-forms-style'), src/index.js runs eval(atob(...)) on a base64 blob appended after module.exports. The decoded payload queries public Ethereum RPC endpoints (1rpc.io, eth.drpc.org, publicnode, blastapi, eth.blockscout.com) for the latest transaction from hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, decodes an IP address from the transaction's to field, then fetches XOR-encrypted payloads from that host at http://<ip>:443/0x/cls and http://<ip>:443/0x/ls (XOR keys 'q4FZkxX{!h,Sr3=@' and 'y-p_>d$0B&@^1aQk'), and executes them via eval() and a detached spawn('node','-e',...) child process. Immediately after the eval runs, src/index.js rewrites itself with fs.writeFileSync(__filename,...) to remove the eval block, so later inspection of the file on disk shows only benign tailwind plugin code. The combination provides arbitrary remote code execution in the installer's Node process, a detached persistent child, an attacker-controlled command channel resilient to takedown (C2 IP rotated via on-chain transactions), and anti-forensic self-erasure.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-forms-style (version 0.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms-style across your stack and pipelines.
If you installed it — respond
tailwindcss-forms-style establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If tailwindcss-forms-style 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 tailwindcss-forms-style 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 tailwindcss-forms-style-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.