Malicious Code Detected in gitkurs Package - Security Alert

gitkurs Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21488: Malicious code in gitkurs (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The gitkurs package is an npm library designed for Git-related functionalities, enabling users to interact with Git repositories programmatically. While it offers various features for developers, it has been identified to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the gitkurs package arises from the inclusion of malicious code, which can compromise the integrity and security of applications that depend on it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall gitkurs

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 measure, consider removing the gitkurs package from your project until a secure version is released. You can do this by running the command: 'npm uninstall gitkurs'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The discovery of malicious code in the gitkurs package poses a significant threat to applications that utilize it. Users are strongly advised to take immediate action by updating or removing the package to safeguard their systems. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for gitkurs →

Share this vulnerability

FAQ

The gitkurs package is used for Git-related functionalities, allowing developers to interact with Git repositories programmatically.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without any signup.

If you cannot update the package right away, consider removing it from your project as a temporary workaround to mitigate risks.

A patch is expected to be released soon. Keep an eye on the package repository for updates and security advisories.

Using the gitkurs package with this vulnerability can lead to unauthorized access, data breaches, and other harmful actions within your application.

How To Fix

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

npm uninstall gitkurs

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