Critical Malicious Code Vulnerability in git-lg Package

git-lg Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21454: Malicious code in git-lg (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The git-lg package is an npm library designed to enhance Git command line functionality. It provides users with additional features and utilities to streamline their Git workflows. However, this package has been found to contain malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the git-lg package. This code can potentially compromise user systems, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from version 0, making it critical for users to take immediate action to mitigate risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall git-lg

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users are advised to remove the git-lg package from their projects until a secure version is released. You can do this by executing the command: 'npm uninstall git-lg'. This will prevent any potential exploitation of the malicious code present in the package.

Conclusion

The git-lg package has been identified as containing malicious code, posing serious security risks to users. Immediate action is required to uninstall the package and monitor for updates. Utilizing tools like Vulert can help keep your projects secure by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for git-lg →

Share this vulnerability

FAQ

The git-lg package is an npm library that enhances Git command line functionality with additional features.

The malicious code can lead to unauthorized access and potential data breaches, compromising user systems.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

As of now, there is no patched version available. Users should monitor the package for updates and remove it from their projects until a secure version is released.

It is recommended to uninstall the git-lg package immediately and monitor for any updates regarding a patched version.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall git-lg

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback