Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

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)

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

4 flagged
1.0.01.1.01.2.02.0.0

Indicators of compromise (SHA-256)

20c367b0508b0c8f2cd7476d0f5f44758ee2fc0fab0ccddd1dd6edc80f655702
a9bd46c99a0d58d9ded0faca080e42efa9015c9bd213c46292e82644117d53ae
53a275ae98500bbefdbd34690ed9e77b520913ea72bb4d7eaf1f526c5660ee80
8878011159a87617e54e257394bf274347f11a8a8b2a1861d47ec384724daa2c
af042e50bb1bde833bb14afdca39a4f7f25084966b80201721ce4de77a1c89e1

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for daisypick (4 malicious versions).

  2. 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.

  3. 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

No. daisypick on npm has been identified as a malicious package (versions 1.0.0, 1.1.0, 1.2.0, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8ppm-gjvm-rvj5IN-MAL-2026-019391IN-MAL-2026-019528IN-MAL-2026-019532IN-MAL-2026-019529

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.

Explore

daisypick (npm) malicious package — MAL-2026-15835 | O3 Security