Which versions of tailwindcssss are malicious?

The following npm versions of tailwindcssss are flagged malicious: 0.2.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.1.1, 1.2.0, 1.3.0, 1.3.1, 1.4.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.7.0, 1.8.0, 1.8.1, 1.9.0, 1.10.0, 1.11.0. Treat any of these as compromised.

How do I remediate tailwindcssss if I installed it?

Remove tailwindcssss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed tailwindcssss — how do I know if it already compromised me?

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

Yes — tailwindcssss is associated with the GHSA-9x5x-r7x3-737h, RLMA-2026-06518, RLUA-2026-10796 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 tailwindcssss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwindcssss (20 malicious versions).

Malicious package

tailwindcssssnpm

Advisory published Jul 30, 2026Updated Sep 24, 2026

tailwindcssss is a confirmed malicious npm package (MAL-2026-11393) that executes malicious code on install (malicious versions 0.2.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwindcssss (npm)

MAL-2026-11393

Immediate action

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

npm uninstall tailwindcssss

What this malware does

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

20 flagged

0.2.01.0.11.0.21.0.31.1.01.1.11.2.01.3.01.3.11.4.01.4.11.5.01.5.11.6.01.7.01.8.01.8.11.9.01.10.01.11.0

Indicators of compromise (SHA-256)

0da18df9b0c152f27cf8431c3ac342f3dd15d7a94ade13a40a7ee7dfcba1614d

d841150ec2e56b92051b0a0b8e3a24a84ac0761ba17a1fdb228b6f44d3d7a763

349c524c8dd37769bbf48f92841689adc3d8a27789ad94c154ba2515792e9119

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for tailwindcssss (20 malicious versions).
If you installed it — respond
Remove tailwindcssss from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If tailwindcssss 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. tailwindcssss on npm has been identified as a malicious package (versions 0.2.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.1.1, 1.2.0, 1.3.0, and 12 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9x5x-r7x3-737hRLMA-2026-06518RLUA-2026-10796

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks tailwindcssss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database