Which versions of tailwind-forms-styles are malicious?

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

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

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

If tailwind-forms-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.

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

Yes — tailwind-forms-styles is associated with the IN-MAL-2026-020060, GHSA-q8wp-7xrg-83rx 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-styles 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 tailwind-forms-styles (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 tailwind-forms-styles across your stack and pipelines.

Malicious package

tailwind-forms-stylesnpm

tailwind-forms-styles is a confirmed malicious npm package (MAL-2026-16195) 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 tailwind-forms-styles (npm)

MAL-2026-16195

Immediate action

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

npm uninstall tailwind-forms-styles

What this malware does

tailwind-forms-styles ships a src/index.js that is fully obfuscated with obfuscator.io (rotated 303-entry string array, hex-named identifiers, control-flow flattening) and bears no relation to the Tailwind forms plugin advertised in the README and src/index.d.ts. On require() the module opens HTTP(S)/zlib streams to Ethereum RPC endpoints (public.blockscout, *.drpc.org, *.publicnode.com) and an etherscan-like transaction indexer, queries transactions for the hardcoded address 0xa322E5f3D311D3080e9aDC2490Ef6f0121063e1a, imports node:child_process spawn, and injects reconstructed strings into the Node global object (_t_u, _t_s, _H, _H2, _r=require, _m=module, _global=global). This is an EtherHiding-style loader that pulls executable payload data from attacker-controlled on-chain storage and hands it to child_process/global-eval sinks, producing arbitrary code execution on the machine that requires the package (e.g. from tailwind.config.js during a build). The package name and the package.json repository field pointing at tailwindlabs/tailwindcss-forms are impersonation of the real @tailwindcss/forms plugin to induce installation.

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

1 flagged

0.5.2

Indicators of compromise (SHA-256)

92f06c2ce29f04ce06cfb494996cb6ffde7aea02af92489abcacf10cbcb7beb2

3394e75d27307e27ab0fed8e037bc3f0c8b3b1e4bd7808c78f3f9c88212383fc

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 tailwind-forms-styles (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 tailwind-forms-styles across your stack and pipelines.
If you installed it — respond
tailwind-forms-styles 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-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-forms-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

No. tailwind-forms-styles 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-020060GHSA-q8wp-7xrg-83rx

References

Credits

Amazon Inspector · finder

Detect & block this

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