Which versions of tailwind-utility-kit are malicious?

The following npm versions of tailwind-utility-kit are flagged malicious: 1.3.2. Treat any of these as compromised.

How do I remediate tailwind-utility-kit if I installed it?

tailwind-utility-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed tailwind-utility-kit — how do I know if it already compromised me?

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

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

Malicious package

tailwind-utility-kitnpm

tailwind-utility-kit is a confirmed malicious npm package (MAL-2026-14190) that steals credentials and exfiltrates sensitive data (malicious version 1.3.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tailwind-utility-kit (npm)

MAL-2026-14190

Immediate action

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

npm uninstall tailwind-utility-kit

What this malware does

The package is advertised as a Tailwind CSS utility library, but the default export assembles a URL from split fragments resolving to https://31.97.137.157:45000/icons/109, fetches JSON from that endpoint, and passes the response's credits field to new Function('require','module',...,'Promise', data.credits), invoking it with require, process, and Buffer. This is arbitrary attacker-controlled code execution on the host that loads the package, with full Node privileges. A decoy setDefaultModule referencing CDN-lookalike domains and a Font Awesome icon path is present as cover-story metadata, and the fragmented URL assembly conceals the bare-IP destination. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are consistent with a browser-credential-stealer payload delivered via the remote loader.

Malicious versions

1 flagged

1.3.2

Indicators of compromise (SHA-256)

39d25399b925f6d37feda28b303576e2ad1672667a44ba9708f5e0ee213089ff

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tailwind-utility-kit (version 1.3.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tailwind-utility-kit across your stack and pipelines.
If you installed it — respond
tailwind-utility-kit is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If tailwind-utility-kit 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-utility-kit 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-utility-kit on npm has been identified as a malicious package (version 1.3.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018258

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tailwind-utility-kit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database