Which versions of tailwind-forms-kit are malicious?

The following npm versions of tailwind-forms-kit are flagged malicious: 0.5.1, 0.5.3, 0.5.5. Treat any of these as compromised.

How do I remediate tailwind-forms-kit if I installed it?

tailwind-forms-kit 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 tailwind-forms-kit — how do I know if it already compromised me?

If tailwind-forms-kit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is tailwind-forms-kit part of a known attack campaign?

Yes — tailwind-forms-kit is associated with the IN-MAL-2026-020784, IN-MAL-2026-021099, GHSA-cpgv-j9j3-hc97, IN-MAL-2026-022538 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 tailwind-forms-kit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-forms-kit (3 malicious versions).

Malicious package

tailwind-forms-kitnpm

Advisory published Sep 30, 2026Updated Nov 4, 2026

tailwind-forms-kit is a confirmed malicious npm package (MAL-2026-17310) that opens a backdoor for remote access (malicious versions 0.5.1, 0.5.3, 0.5.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-forms-kit (npm)

MAL-2026-17310

Immediate action

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

npm uninstall tailwind-forms-kit

What this malware does

npm package [email protected] impersonates the @tailwindcss/forms plugin: the package.json name field is ' tailwind-forms-kit' (with a leading space), the README mirrors tailwindlabs/tailwindcss-forms, and the repository field points at the legitimate tailwindlabs/tailwindcss-forms repo. The shipped src/index.js (the package's main entry) is not a Tailwind plugin. It is a single-line obfuscator.io-obfuscated loader (string array _0x18ab with 303 entries, rotate/shift IIFE, decoder _0x35ba, hex-named variables) that at require() time imports node:http, node:https, node:zlib, and spawn from node:child_process. It reassembles at runtime a hardcoded Ethereum sender address (0xa322E5f39aDC2490EfD311D3080e6f0121063e1a) and a list of public Ethereum RPC endpoints and an Etherscan-style indexer URL (publicnode.com, 1rpc.io, drpc.org, blockscout) from string-array indices, queries the indexer for that sender's transaction list ('?module=ac...on=txlist&address=...'), reconstructs a payload from the returned on-chain transaction data, and hands the reconstructed bytes to node:child_process spawn / dynamic execution via global slots (_t_u, _t_s, _H, _H2). This is the EtherHiding blockchain-hosted-C2 pattern: whoever controls the sender address controls arbitrary code executed on any host that installs or requires the package, with no version pin, no hash verification, and blockchain-data transport chosen to evade domain and URL blocklists. The Tailwind branding, copied README, and misleading repository URL are cover for the loader.

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

3 flagged

0.5.10.5.30.5.5

Indicators of compromise (SHA-256)

a1083ea1ddf83f29a443e7ba4b24db0d24da35dfd0a9d0ac032ae20501ac57ea

0ddad6b159f2cfa136e4e3f97e86ab0b901a4fb083d1a18987f9daf48f66306e

0e4d1c766732546052e1051145bef0096541b69f049903b4ae42be0572c6b6e8

4ee4c4034a7383c29689c245cbed08ba7dff332542c47a058607651e7b3142e5

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for tailwind-forms-kit (3 malicious versions).
If you installed it — respond
tailwind-forms-kit 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 tailwind-forms-kit was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. tailwind-forms-kit on npm has been identified as a malicious package (versions 0.5.1, 0.5.3, 0.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020784IN-MAL-2026-021099GHSA-cpgv-j9j3-hc97IN-MAL-2026-022538

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-forms-kit-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