Malware in gitlens
Malware was discovered in the gitlens npm package. Systems with the package installed or running are considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with gitlens installed or running
- Ecosystems
- Attack vectors
- Affected entities
- gitlensnpm package
A critical malware incident was identified in the gitlens npm package. According to the GitHub Security Advisory (GHSA-mgwg-48mg-h7pg), any computer with 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 removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting the npm ecosystem.
Indicators of compromise
- Packages
- gitlens
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the gitlens package from all affected systems
- Conduct a full security audit of any system that had gitlens 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
- Monitor for any signs of persistent malware that may remain after package removal
Sources
- GitHub Advisory GHSA-mgwg-48mg-h7pg · GitHub Advisory Database
Cite this entry
"Malware in gitlens." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 9, 2026; last updated July 9, 2026. https://supplychainattack.org/incident/malware-in-gitlens-h41uih
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 myclaude-code
Malware was discovered in the npm package myclaude-code. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
npmCompromised package - resolvedcritical
Malware in clavue
The npm package clavue contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.
npmCompromised package - containedcritical
Malware in airkey-mfa-react
Malware was discovered in the npm package airkey-mfa-react. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a different computer.
npmCompromised package - resolvedcritical
Malware in fusion-client
The npm package fusion-client contained malware that provided full system compromise to attackers. Any computer with the package installed should be considered fully compromised and all secrets and keys rotated from a different machine.
npmCompromised package