Malware in gx-npm-ui
Malware was discovered in the npm package gx-npm-ui, 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.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- gx-npm-ui
A malware incident was identified in the npm package gx-npm-ui. According to the GitHub Advisory (GHSA-5jpv-9x2f-72jj), 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 computer. While the package should be removed, there is no guarantee that removing it will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe incident was published on 2026-06-29 via the GitHub advisory feed.
Indicators of compromise
- Packages
- gx-npm-ui
Remediation
- Remove the gx-npm-ui package from all affected systems
- Rotate all secrets and keys stored on affected computers from a different, uncompromised computer
- Assume full system compromise and conduct a thorough security audit of affected systems
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if possible
Sources
- GitHub Advisory GHSA-5jpv-9x2f-72jj · GitHub Advisory Database
Cite this entry
"Malware in gx-npm-ui." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-gx-npm-ui-1lfsey
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in @vpms/design-system
Malware was discovered in the npm package @vpms/design-system. 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 - activecritical
Malware in unsafe-malicious-package
Malware discovered in the npm package unsafe-malicious-package. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in ts-ankle
The npm package ts-ankle was found to contain malware. Any system with the package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.
npmCompromised package - resolvedcritical
Malware in velocityfix
The npm package velocityfix contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package