Which versions of tailwind-style-override are malicious?

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

How do I remediate tailwind-style-override if I installed it?

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

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

Yes — tailwind-style-override is associated with the RLMA-2025-05960, RLUA-2025-06510, RLUA-2026-01606 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-style-override 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-style-override (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 tailwind-style-override across your stack and pipelines.

Malicious package

tailwind-style-overridenpm

Malicious code in tailwind-style-override (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191594

Immediate action

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

npm uninstall tailwind-style-override

What this malware does

The package tailwind-style-override was found to contain malicious code.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

ff9492c5764a33399e5bc561f7f8c3d47e7506db50a32cfdf2aa8ee4f6d3f720

f70c1280fa4f70d4161ef2634dd7eb7f7b59b51cac954465a8d1aad2a1ae5763

47f4c533222abd8a034e68345a9055eb86d815d6971140403507584dfb4909c3

9592ba72faa3e016a43d44e1eaa80239490fc4f57c3ae03bb7278755aec95412

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 tailwind-style-override (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 tailwind-style-override across your stack and pipelines.
If you installed it — respond
Remove tailwind-style-override 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-style-override 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-style-override 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-style-override 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-05960RLUA-2025-06510RLUA-2026-01606

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks tailwind-style-override-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