Which versions of tailwindcss-forms-ui are malicious?

The following npm versions of tailwindcss-forms-ui are flagged malicious: 0.5.2. Treat any of these as compromised.

How do I remediate tailwindcss-forms-ui if I installed it?

tailwindcss-forms-ui 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.

I already installed tailwindcss-forms-ui — how do I know if it already compromised me?

If tailwindcss-forms-ui 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.

Is tailwindcss-forms-ui part of a known attack campaign?

Yes — tailwindcss-forms-ui is associated with the IN-MAL-2026-020188 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find tailwindcss-forms-ui across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-forms-ui (version 0.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms-ui across your stack and pipelines.

Malicious package

tailwindcss-forms-uinpm

tailwindcss-forms-ui is a confirmed malicious npm package (MAL-2026-16295) that opens a backdoor for remote access (malicious version 0.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcss-forms-ui (npm)

MAL-2026-16295

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall tailwindcss-forms-ui

What this malware does

The package name typosquats @tailwindcss/forms but its main entry src/index.js is a 39 KB obfuscator.io bundle (303-entry rotating string array, hex-named identifiers, control-flow flattening) with no Tailwind/CSS functionality. On require(), the module attaches require and module to global scope, then queries Ethereum JSON-RPC endpoints (eth.publicnode.com, 1rpc.io/eth, eth-mainnet.public.blastapi.io, eth.drpc.org) and Etherscan/Blockscout txlist APIs for transactions from the hardcoded sender address 0xa322E5f39aDC2490EfD311D3080e6f0121063e1a, decompresses the returned transaction data (gzip/deflate/brotli), and passes it to code-construction and node:child_process.spawn sinks. The hardcoded sender's on-chain transactions are a mutable, attacker-controlled payload channel (EtherHiding pattern), granting arbitrary code execution on any installer that require()s the module.

Malicious versions

1 flagged

0.5.2

Indicators of compromise (SHA-256)

6f2bdfef8937b1e6ef4979181693e00adbdfbe7521b8b240268f76beff8b3be8

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-forms-ui (version 0.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms-ui across your stack and pipelines.
If you installed it — respond
tailwindcss-forms-ui 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-ui 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-ui 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

No. tailwindcss-forms-ui on npm has been identified as a malicious package (version 0.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020188

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-forms-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database