Which versions of daisypick are malicious?

The following npm versions of daisypick are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate daisypick if I installed it?

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.

I already installed daisypick — how do I know if it already compromised me?

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

Yes — daisypick is associated with the GHSA-8ppm-gjvm-rvj5, IN-MAL-2026-019391 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 daisypick 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 daisypick (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging daisypick across your stack and pipelines.

Malicious package

daisypicknpm

daisypick is a confirmed malicious npm package (MAL-2026-15835) that steals credentials and exfiltrates sensitive data (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in daisypick (npm)

MAL-2026-15835

Immediate action

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

npm uninstall daisypick

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

1 flagged

1.2.0

Indicators of compromise (SHA-256)

20c367b0508b0c8f2cd7476d0f5f44758ee2fc0fab0ccddd1dd6edc80f655702

a9bd46c99a0d58d9ded0faca080e42efa9015c9bd213c46292e82644117d53ae

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 daisypick (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging daisypick across your stack and pipelines.
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 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 daisypick 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. daisypick on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8ppm-gjvm-rvj5IN-MAL-2026-019391

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database