Which versions of tailwind-state are malicious?

The following npm versions of tailwind-state are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate tailwind-state if I installed it?

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

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

Yes — tailwind-state is associated with the RLMA-2025-05959, RLUA-2025-06509, RLUA-2026-01605 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-state across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tailwind-state (version 1.0.3).

Malicious package

tailwind-statenpm

Advisory published Dec 1, 2025Updated Mar 19, 2026

tailwind-state is a confirmed malicious npm package (MAL-2025-191593) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-state (npm)

MAL-2025-191593

Immediate action

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

npm uninstall tailwind-state

What this malware does

The package tailwind-state was found to contain malicious code.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

5e671748e7d42fab74c13b0a53a365a668e732f63ea4ae54b8bf31c2567d40a5

6a38d486faa9b2c50df466ad3d25dfa289548864c0fde19ad24d7da6421db683

299ea83f5e351b1ef1cc9dcafbf99ebf9a3aac57d8f2ee800de6f4ddfc7814ab

465e0e996999a2910c579cf861c1ea4bf6508fe20e5c65782f7379d011ac4ce7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05959RLUA-2025-06509RLUA-2026-01605

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tailwind-state-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