Critical Malicious Code Vulnerability in bwtgithub Package

bwtgithub Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16394: Malicious code in bwtgithub (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 bwtgithub package is an npm library designed for various functionalities related to GitHub interactions. It is widely used in JavaScript projects for automating tasks and enhancing developer productivity. However, this package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the bwtgithub package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or even complete system takeover. 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 bwtgithub

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. Review your project's dependencies and replace bwtgithub with a trusted library until the issue is resolved.

Conclusion

The bwtgithub package contains a critical vulnerability due to malicious code that can severely impact the security of applications. It is crucial for developers to take immediate action by removing the package and considering alternatives. Regularly monitoring dependencies and utilizing tools like Vulert can help maintain application security.

See every vulnerability recorded for bwtgithub →

Share this vulnerability

FAQ

bwtgithub is an npm package used for automating GitHub-related tasks in JavaScript applications.

The malicious code was identified by security researchers from Amazon Inspector, who reported the vulnerability to the community.

Using the bwtgithub package can lead to unauthorized access to your application, data breaches, and potential system compromise.

Yes, you can use Vulert, a tool that monitors open-source vulnerabilities in your software. You can check your application by visiting Vulert Scanner without needing to sign up.

If immediate removal is not possible, consider implementing strict access controls and monitoring your application for any suspicious activity until you can replace the package.

How To Fix

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

npm uninstall bwtgithub

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