Malicious Code Injection in farazali Package: npm Vulnerability Overview

farazali Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171195: Malicious code in farazali (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 farazali package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry but has been compromised to include malicious code. The vulnerability stems from the package's ability to modify critical files, such as package.json, which can lead to significant security risks for developers and their applications.

Vulnerability Detail

The farazali package contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is part of a broader scheme to inflate developer reputation scores for token rewards. The malicious payload continuously republishes variants of the package, polluting the npm registry and potentially compromising other packages that depend on it. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall farazali

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, you can avoid using the farazali package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any changes using tools like Vulert, which can alert you to vulnerabilities in real-time.

Conclusion

The farazali package has been identified as containing malicious code that poses significant risks to developers and their applications. Immediate action is required to remove the package and monitor for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your projects.

See every vulnerability recorded for farazali →

Share this vulnerability

FAQ

The farazali package is an npm package associated with the tea.xyz token reward campaign, designed to facilitate various functionalities within the npm ecosystem.

The malicious code modifies your package.json file, potentially compromising your application's integrity and security by removing private flags and altering version numbers.

You should uninstall the farazali package immediately using the command: npm uninstall farazali, and monitor your project for any further vulnerabilities.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without requiring access to the code or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall farazali

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