Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @crowdstrike published 9 malicious packages. See the full campaign →
Malicious package

@crowdstrike/tailwind-toucan-basenpm

@crowdstrike/tailwind-toucan-base is a confirmed malicious npm package (MAL-2025-47237) that steals credentials and exfiltrates sensitive data (malicious versions 5.0.1, 5.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @crowdstrike/tailwind-toucan-base (npm)

MAL-2025-47237
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @crowdstrike/tailwind-toucan-base

What this malware does

The package was compromised and malicious code added.

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

2 flagged
5.0.15.0.2

Indicators of compromise (SHA-256)

815645af1286f8262a60ed5ee1cfb7b699786a707007300ea5c62602046d2460
10e1aa9c482399efb15b1858a7cec6ffa1d473d20845d0bda914fc37f3c9f896
52ee482530a441a0646c197b681216b9e2c930df3e7b2b2d212a9512b2508893
5ad9278ed31797c3b1829bedce9ea014a614520d3c8a3354c37d8c3d0a5371c3

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @crowdstrike/tailwind-toucan-base (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @crowdstrike/tailwind-toucan-base across your stack and pipelines.

  2. If you installed it — respond

    @crowdstrike/tailwind-toucan-base 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 @crowdstrike/tailwind-toucan-base 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.

  4. How O3 protects you

    O3 blocks @crowdstrike/tailwind-toucan-base 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. @crowdstrike/tailwind-toucan-base on npm has been identified as a malicious package (versions 5.0.1, 5.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f679-rpph-9qxf

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @crowdstrike/tailwind-toucan-base-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

@crowdstrike/tailwind-toucan-base (npm) malicious package — MAL-2025-47237 | O3 Security