Malware in ui-weave
Malware was discovered in the npm package ui-weave, 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.
- Disclosed
- Last updated
- Blast radius
- Any system with ui-weave installed or running
- Ecosystems
- Attack vectors
- Affected entities
- ui-weave
A critical malware incident was identified in the npm package ui-weave. According to the GitHub Advisory (GHSA-x2w5-px4q-j9wq), any computer that has this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package will remove all malicious software resulting from the installation.\n\nThis represents a severe supply chain attack through package distribution, affecting all users who installed or ran the compromised ui-weave package.
Indicators of compromise
- Packages
- ui-weave
Remediation
- Immediately rotate all secrets and keys from a different, uncompromised computer
- Remove the ui-weave package from all affected systems
- Conduct a full security audit of any system that had ui-weave installed
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
- Check for any unauthorized access or lateral movement from affected systems
Sources
- GitHub Advisory GHSA-x2w5-px4q-j9wq · GitHub Advisory Database
Cite this entry
"Malware in ui-weave." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 9, 2026; last updated June 9, 2026. https://supplychainattack.org/incident/malware-in-ui-weave-z42akj
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for 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 - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package