Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in lucide-next

Malware was discovered in the lucide-next npm package. Systems with the package installed or running are considered fully compromised and require immediate remediation including secret rotation and package removal.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with lucide-next installed or running
Ecosystems
Attack vectors
Affected entities
  • lucide-nextnpm package

A critical malware incident was identified in the lucide-next npm package. According to the GitHub Advisory (GHSA-gqhv-66pr-h35f), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. While the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nThis represents a supply chain attack through a compromised package in the npm ecosystem, affecting all users who installed or ran lucide-next.

Indicators of compromise

Packages
  • lucide-next

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the lucide-next package from all affected systems
  • Perform a full security audit and malware scan of any system that had lucide-next installed or running
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
  • Notify any services or systems that may have been accessed from the compromised computer

Sources

  1. GitHub Advisory GHSA-gqhv-66pr-h35f · GitHub Advisory Database

Cite this entry

"Malware in lucide-next." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 16, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-lucide-next-150mr9

Suggest a correction

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

  1. containedcritical

    Malware in janus-flow

    Malware was discovered in the npm package janus-flow, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  2. containedcritical

    Malware in flow-lending-sdk

    Malware was discovered in the npm package flow-lending-sdk. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  3. activecritical

    Malware in auth-basic-vault

    Malware discovered in the npm package auth-basic-vault. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  4. containedcritical

    Malware in ttspc-server-sample

    The npm package ttspc-server-sample contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package