tailwind-kinetic (npm) · Malicious Code
Affects tailwind-kineticSource GCVE Database
Malicious package : remove tailwind-kinetic and rotate any secrets on hosts that installed it.
Data as of 29 Oct 2026, 18:52 UTC
Malicious package
Published to npm · OSV MAL-2026-18084
What to do
Remove tailwind-kinetic 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 |
|---|---|---|
| npmtailwind-kinetic | 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 tailwind-kinetic versions 2.0.6 and 2.0.8 are part of a malicious campaign linked to fake job interviews. The package itself contains no direct install scripts or network code, but it depends on a private scoped package that requires an npm token embedded in a lure repository. This private dependency executes code when the plugin is loaded, potentially compromising the host system. Multiple related malicious packages were published over several months. Although the shipped package content does not show typical supply-chain attack fingerprints, any system with this package installed should be considered fully compromised.
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/tailwind-kinetic/v/2.0.8 (opens in a new tab)
- npmjs.com/package/tailwind-kinetic/v/2.0.6 (opens in a new tab)
- github.com/advisories/GHSA-j2r4-xxhh-xx58 (opens in a new tab)