Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in clsx-tailwind

Malware was discovered in the npm package clsx-tailwind. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with clsx-tailwind installed or running
Ecosystems
Attack vectors
Affected entities
  • clsx-tailwindnpm package containing malware

The npm package clsx-tailwind was found to contain malware. According to the GitHub Advisory (GHSA-373j-j35f-q4gx), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The malicious package should be removed, though complete removal of all malicious artifacts cannot be guaranteed due to the potential for full system compromise.\n\nUsers should assume that an outside entity may have gained full control of affected systems during the package installation period.

Indicators of compromise

Packages
  • clsx-tailwind

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the clsx-tailwind package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Review system logs and access patterns for signs of unauthorized activity
  • Consider full system reimaging if the system handles sensitive data or credentials

Sources

  1. GitHub Advisory GHSA-373j-j35f-q4gx · GitHub Advisory Database

Cite this entry

"Malware in clsx-tailwind." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-clsx-tailwind-1eva5y

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. activecritical

    Malware in chain-manager

    Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malicious code in @finxsecdemo/utils (npm)

    The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.

    npmCompromised package
  3. containedcritical

    Malware in @bowozzz/baileys

    The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  4. containedcritical

    Malicious code in blots (npm)

    The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.

    npmCompromised package