Critical Malicious Code Vulnerability in @fazzcodestudio/fbot Package

@fazzcodestudio/fbot Updated 12 Oct 2026

Summary

12/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17821: Malicious code in @fazzcodestudio/fbot (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 @fazzcodestudio/fbot package is an npm library designed for creating chatbots with various functionalities. It allows developers to integrate bot capabilities into their applications easily. However, this package has been identified to contain malicious code, posing a significant security risk to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @fazzcodestudio/fbot package. Any computer with this package installed is considered fully compromised, as it may allow unauthorized access to sensitive information, including secrets and keys stored on the system. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall @fazzcodestudio/fbot

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 effective workarounds for this vulnerability. The only recommended action is to uninstall the package and rotate any sensitive information that may have been compromised.

Conclusion

The @fazzcodestudio/fbot package contains malicious code that compromises the security of any system it is installed on. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @fazzcodestudio/fbot →

Share this vulnerability

FAQ

You should uninstall the package immediately and rotate any secrets or keys stored on your system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

The risks include unauthorized access to sensitive information, potential data breaches, and loss of control over the affected systems.

No patch is available for the @fazzcodestudio/fbot package. The only solution is to uninstall the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall @fazzcodestudio/fbot

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