daisypicknpm
Advisory published Updated
daisypick is a confirmed malicious npm package (MAL-2026-15835) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.1.0, 1.2.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in daisypick (npm)
What this malware does
The package presents itself as a Tailwind CSS color/service-worker helper, but the daisypick/plugin export reads a URL from node_modules/.bin/manifest.json, downloads a JavaScript body over the network via fetchScript, deletes the manifest file after reading it, and passes the downloaded code to resolveDelegate. resolveDelegate reconstructs the string constructor at runtime by shuffling the seed strings METHOD_SEED = "gbcweftcoqstauctorhijklmnopdrsruvnxy" and TOKEN_SEED with colorToHex, indexes resolver[methodName] to obtain the Function constructor, and invokes the resulting function inside withModuleContext, executing the fetched code in the Node process with require, module, and __filename bound in. The fetched URL is unpinned and unverified, and the manifest is unlinked after use. Any developer adding daisypick/plugin to a Tailwind config therefore causes arbitrary remote JavaScript to run in-process on the build machine on every Tailwind build, with the Function-constructor lookup deliberately hidden behind color-utility naming to evade static inspection.
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
Search your lockfiles and build artifacts for daisypick (4 malicious versions).
If you installed it — respond
daisypick 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 daisypick was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks daisypick-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.