clsx-tailwindnpm
clsx-tailwind is a confirmed malicious npm package (MAL-2026-5625) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in clsx-tailwind (npm)
What this malware does
Package advertises a trivial Tailwind class-name merger (a 5-line cn() helper) but its main entry dist/index.js unconditionally requires dist/lib/lib.min.js, which runs at import time. That file (a) assigns require and module onto the global object so subsequently-evaluated code can resolve modules without containing literal require/module tokens, (b) reconstructs method names and an executable body via a hand-rolled string-shuffle decoder (YWG), and (c) resolves YWG[OSN] to Function.constructor and immediately invokes it on the decoded blob, evaluating obfuscated code on every consumer's require('clsx-tailwind'). The combination of heavy string-shuffle obfuscation, dynamic Function() evaluation of the decoded output, leaking require/module to the global namespace, and a payload entirely unrelated to the package's advertised purpose is the canonical malicious-payload shape. Any process that imports this package executes attacker-controlled code with the privileges of the host application.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for clsx-tailwind (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging clsx-tailwind across your stack and pipelines.
If you installed it — respond
clsx-tailwind 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 clsx-tailwind 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 clsx-tailwind 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks clsx-tailwind-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.