Which versions of better-tailwindcss are malicious?

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

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

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

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

Yes — better-tailwindcss is associated with the IN-MAL-2026-010391, RLMA-2026-06084 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 better-tailwindcss 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 better-tailwindcss (version 4.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging better-tailwindcss across your stack and pipelines.

Malicious package

better-tailwindcssnpm

better-tailwindcss is a confirmed malicious npm package (MAL-2026-10550) that executes malicious code on install (malicious version 4.6.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in better-tailwindcss (npm)

MAL-2026-10550

Immediate action

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

npm uninstall better-tailwindcss

What this malware does

The package publishes under the name of the legitimate better-tailwindcss project but its package.json declares both a runtime and dev dependency on better-tailwindcss resolved from http://pack.nppacks.com/npm/better-tailwindcss — a plain-HTTP, non-registry host with no integrity hash and no TLS. On npm install, npm fetches and installs that arbitrary, mutable tarball, and any install/postinstall scripts inside it execute on the installer's machine. The shipped code itself is a Babel plugin clone unrelated to the real better-tailwindcss project (a tailwind ESLint plugin) and carries a self-label describing the package as being for 'Security Research Testing Purpose,' confirming it is a namespace squat used as a delivery vehicle for code hosted at pack.nppacks.com.

Malicious versions

1 flagged

4.6.3

Indicators of compromise (SHA-256)

302c3b7766a431cefe81d41434fd4c5aae74aacec230488bd004eca18cbe8dff

3c82f6e57ed9b9090d551a7a490887064caebce9ab0ff9ad1db216c276bc6373

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 better-tailwindcss (version 4.6.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging better-tailwindcss across your stack and pipelines.
If you installed it — respond
Remove better-tailwindcss 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 better-tailwindcss 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 better-tailwindcss 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. better-tailwindcss on npm has been identified as a malicious package (version 4.6.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010391RLMA-2026-06084

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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