Malicious Code Detected in bbbgit Package - Security Alert

bbbgit Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15532: Malicious code in bbbgit (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

bbbgit is an npm package designed for Git operations, providing functionalities that streamline interactions with Git repositories. However, it has been identified to contain malicious code, posing significant security risks to users who integrate it into their applications. This vulnerability can lead to unauthorized access or data breaches.

Vulnerability Detail

The bbbgit package has been found to contain malicious code that was introduced in version 0 and has not been addressed in subsequent releases. This vulnerability can allow attackers to execute harmful scripts, potentially compromising user data and system integrity. Users of this package are at risk of exploitation, which could lead to severe consequences such as data loss or unauthorized access to sensitive information.

How To Fix

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

npm uninstall bbbgit

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 using alternative packages that provide similar functionality without the associated risks. Review your project dependencies and replace bbbgit with a safer option until a secure version is released.

Conclusion

The discovery of malicious code in the bbbgit package poses a serious threat to users. It is essential to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for bbbgit →

Share this vulnerability

FAQ

bbbgit is an npm package that facilitates Git operations, but it has been compromised with malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Remove the bbbgit package from your project immediately and look for alternative packages to ensure your application's security.

As of now, there is no patched version available. It is recommended to remove the package until a secure version is released.

Vulert uses the package-lock.json file to monitor and alert users in real-time for any open-source vulnerabilities without requiring access to the code or installation.

How To Fix

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

npm uninstall bbbgit

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