Which versions of tailwindcss-forms are malicious?

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

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

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

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

Yes — tailwindcss-forms is associated with the RLMA-2025-05961, RLUA-2025-06511, RLUA-2026-01607 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 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 tailwindcss-forms (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms across your stack and pipelines.

Malicious package

tailwindcss-formsnpm

Malicious code in tailwindcss-forms (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191595

Immediate action

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

npm uninstall tailwindcss-forms

What this malware does

The package tailwindcss-forms was found to contain malicious code.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

e20a355d1779a03099a213f7f35e6272f19168d5fb06ddec939a81910f7c3f1f

65ee27d0caf9bfc7ff677eb3a3ab32742a19c31bc8418b532bbf925c6a5c385b

84175205fdc8baabb3d361c52f189b83818b8a766521a69423e6e8c7b2539459

69c937a216545a949ab3f59ead6816480f08f8efdc8861dc27e7b9848dd78b02

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwindcss-forms (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwindcss-forms across your stack and pipelines.
If you installed it — respond
Remove tailwindcss-forms 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 tailwindcss-forms 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 tailwindcss-forms 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. tailwindcss-forms 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-05961RLUA-2025-06511RLUA-2026-01607

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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