tailwindcss-effect-lab (npm) · Malicious Code
Affects tailwindcss-effect-labSource GCVE Database
Malicious package : remove tailwindcss-effect-lab and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 17:53 UTC
Malicious package
Published to npm · OSV MAL-2026-18087
What to do
Remove tailwindcss-effect-lab from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmtailwindcss-effect-lab | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package tailwindcss-effect-lab versions 0.0.0-stage and 1.6.7 is associated with a malicious campaign involving a private dependency that executes code when the plugin is loaded. The payload resides in a private scoped package that requires an npm token to access, preventing public retrieval of the malicious code. The publicly available tarball does not contain install scripts or network code. Multiple related packages were published under different accounts over several months. An Amazon Inspector analysis found no evidence of typical supply-chain attack behaviors such as network activity or credential theft in the examined package.
References
- osv.dev/vulnerability/MAL-2026-17665 (opens in a new tab)
- osv.dev/vulnerability/MAL-2026-17666 (opens in a new tab)
- osv.dev/vulnerability/MAL-2026-17667 (opens in a new tab)
- pkgwarden.com/incidents/fake-interview-tailwind-plugins-npm-october-2026/ (opens in a new tab)
- npmjs.com/package/tailwindcss-effect-lab/v/1.6.7 (opens in a new tab)