Malicious Code Detected in fazilet-cli Package

fazilet-cli Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20260: Malicious code in fazilet-cli (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 fazilet-cli package is a command-line interface tool designed for various functionalities within the Node.js ecosystem. It is utilized by developers for streamlining tasks and automating processes. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the fazilet-cli package stems from the inclusion of malicious code that can compromise the security of systems utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions. The issue originates from 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 fazilet-cli

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, users can avoid using the fazilet-cli package until a secure version is released. Alternatively, consider using other CLI tools that provide similar functionalities without the associated risks.

Conclusion

The fazilet-cli package has been identified to contain malicious code, posing serious security risks to users. It is crucial to update the package to a secure version or consider alternative tools until a fix is available. Regular monitoring of dependencies is recommended to maintain application security.

See every vulnerability recorded for fazilet-cli →

Share this vulnerability

FAQ

fazilet-cli is a command-line interface tool used in the Node.js ecosystem for automating tasks and streamlining development processes.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of systems that use this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If immediate updates are not possible, consider using alternative CLI tools or refrain from using fazilet-cli until a secure version is released.

Utilize tools like Vulert to monitor your package-lock.json for vulnerabilities and receive real-time alerts.

How To Fix

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

npm uninstall fazilet-cli

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