Which versions of tailwindcss-forms-styles are malicious?

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

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

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

If tailwindcss-forms-styles 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 tailwindcss-forms-styles part of a known attack campaign?

Yes — tailwindcss-forms-styles is associated with the IN-MAL-2026-020952 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-styles across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwindcss-forms-styles (version 0.5.1).

Malicious package

tailwindcss-forms-stylesnpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

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

Malicious code in tailwindcss-forms-styles (npm)

MAL-2026-17524

Immediate action

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

npm uninstall tailwindcss-forms-styles

What this malware does

The package name tailwindcss-forms-styles mimics the legitimate @tailwindcss/forms plugin, and its src/index.js copies that plugin's code verbatim as cover. Above the cover code, a top-level IIFE joins a ~140-element base64 string array, atob()-decodes it, and eval()s the result. The decoded loader queries public Ethereum RPC/Blockscout endpoints for the most recent transaction sent by hardcoded address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a, parses two IPv4 addresses out of the transaction recipient field, downloads an XOR-encoded JavaScript payload from staging URLs of the form http://<ip>:443/0x/cls and http://<ip>:443/0x/ls, and executes it via eval and a detached spawn('node', ['-e',...]) child process. Because the IIFE runs at module load, any consumer that performs require('tailwindcss-forms-styles') triggers remote code execution on the installer, with the command-and-control endpoint resolved dynamically from the blockchain so the C2 can be rotated without changing the package.

Malicious versions

1 flagged

0.5.1

Indicators of compromise (SHA-256)

587d9a389f35a8ec2d3ed714c90f7daa43feb6875f4ce2e4280f5ce19569d895

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for tailwindcss-forms-styles (version 0.5.1).
If you installed it — respond
tailwindcss-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 tailwindcss-forms-styles 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. tailwindcss-forms-styles on npm has been identified as a malicious package (version 0.5.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020952

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwindcss-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