Critical Malicious Code Vulnerability in github-badge-bot Package

github-badge-bot Updated 05 Jan 2026

Summary

05/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-46: Malicious code in github-badge-bot (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The github-badge-bot package is an npm module designed to facilitate the integration of GitHub badges into projects. It allows users to display various metrics and statuses related to their GitHub repositories. However, this package has been identified as containing malicious code, which poses a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the github-badge-bot package. This code can compromise the security of any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionalities that can lead to severe security breaches.

How To Fix

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

npm uninstall github-badge-bot

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

There are no specific workarounds available for this vulnerability. The only recommended action is to uninstall the package and secure any sensitive information that may have been compromised.

Conclusion

The github-badge-bot package has been identified as containing malicious code, posing a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor their projects for vulnerabilities.

See every vulnerability recorded for github-badge-bot →

Share this vulnerability

FAQ

The github-badge-bot package is an npm module that allows users to integrate GitHub badges into their projects, displaying various metrics and statuses.

The malicious code can compromise your system, potentially allowing unauthorized access to sensitive information such as secrets and keys stored on your computer.

If you have the github-badge-bot package installed, you should uninstall it immediately and rotate any sensitive information stored on your system.

No, there is currently no patched version of the github-badge-bot package available. The only solution is to uninstall the package.

You can use Vulert, a tool that monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall github-badge-bot

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