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
Malicious code in ladash-cli (npm)
ladash-cli is a typosquat package on npm that executes malicious code during installation. The postinstall script downloads and executes a Windows binary, with special handling for WSL environments to compromise the underlying Windows host.
npmTyposquattingCompromised package - containedcritical
Malicious code in comand (npm)
The npm package 'comand' contained malicious code that executed automatically on install via postinstall.js, exfiltrating platform information and downloading an unsigned executable (main.exe) to Windows systems or via WSL PowerShell bridges. The package name appears to be a typosquat of 'command', and the GitHub owner (braz1) does not match the npm publisher.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in core-js-gns (npm)
The npm package core-js-gns contained malicious code in its postinstall hook that exfiltrated system information and executed remotely-fetched Python code on developer machines. The package name was a typosquat of the legitimate core-js library.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in comander-lib (npm)
comander-lib@1.0.0 is a typosquat of the legitimate `commander` package containing malicious code. The package's postinstall script exfiltrates system information to a C2 server and downloads and executes a Windows payload, with capability to escape WSL/Linux sandboxes via PowerShell.
npmTyposquattingCompromised package