Malicious Code Detected in githsc Package: A Critical Security Alert

githsc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21481: Malicious code in githsc (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 githsc package is an npm library designed to facilitate interactions with GitHub repositories. It offers functionalities such as repository management and automation of GitHub workflows. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the githsc package stems from the inclusion of malicious code that can compromise user data and system integrity. This code was introduced in version 0 and can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. Users of this package are at risk of having their sensitive information exposed or manipulated by malicious actors.

How To Fix

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

npm uninstall githsc

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, consider using alternative packages that provide similar functionalities without the associated risks. Additionally, you can implement security measures such as code reviews and dependency audits to mitigate potential threats.

Conclusion

The discovery of malicious code in the githsc package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to protect their applications and data by removing the affected package and considering alternatives.

See every vulnerability recorded for githsc →

Share this vulnerability

FAQ

githsc is an npm package designed for managing and automating tasks related to GitHub repositories.

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

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Immediately remove the githsc package and check for any updates or patches. Consider using alternative packages.

Regularly audit your dependencies, keep them updated, and utilize tools like Vulert for real-time monitoring of vulnerabilities.

How To Fix

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

npm uninstall githsc

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