Malicious Code Injection in farhanzain Package: npm Vulnerability Overview

farhanzain Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171201: Malicious code in farhanzain (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 farhanzain package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards.

Vulnerability Detail

The vulnerability in the farhanzain package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload can potentially affect developers who rely on the npm registry for legitimate packages, leading to security risks and loss of trust.

How To Fix

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

npm uninstall farhanzain

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 remove the farhanzain package from your project by executing the command: 'npm uninstall farhanzain'. This will prevent any malicious code from executing until a safe version is available.

Conclusion

The farhanzain package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can aid in maintaining the security of your software.

See every vulnerability recorded for farhanzain →

Share this vulnerability

FAQ

The farhanzain package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your project and potentially affecting other dependencies.

You should uninstall the farhanzain package immediately and monitor for any updates or patches that may be released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly updating your packages, using tools like Vulert for monitoring, and auditing your dependencies can help prevent vulnerabilities.

How To Fix

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

npm uninstall farhanzain

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