Malicious Code Injection in faressorbet Package: npm Vulnerability Overview

faressorbet Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171197: Malicious code in faressorbet (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 faressorbet package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the faressorbet package stems from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts designed to automatically publish derivative packages with altered metadata. The malicious payload modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which can lead to reputation inflation and pollution of the npm registry. This poses risks such as unauthorized access to sensitive data and potential exploitation of applications relying on these packages.

How To Fix

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

npm uninstall faressorbet

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 faressorbet package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The faressorbet package poses a significant security risk due to its malicious code designed to exploit npm's publishing system. It is essential to remove this package from your projects and monitor for any updates or alternatives to maintain the security and integrity of your applications.

See every vulnerability recorded for faressorbet →

Share this vulnerability

FAQ

faressorbet is an npm package that has been identified as part of a malicious campaign targeting the npm registry, aimed at inflating developer reputation scores.

The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially exposing sensitive data and compromising application integrity.

You should uninstall the faressorbet package immediately using the command npm uninstall faressorbet to mitigate any risks.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application using the Vulert playground without any signup.

Yes, consider using other reputable packages that provide similar functionality, ensuring they are well-maintained and have a good security track record.

How To Fix

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

npm uninstall faressorbet

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