Malicious Code Injection in fine_vulture_0xrequest Package

fine_vulture_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102733: Malicious code in fine_vulture_0xrequest (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The fine_vulture_0xrequest package is part of a broader ecosystem of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses significant risks to the integrity of the npm registry and can lead to the proliferation of malicious software.

Vulnerability Detail

The vulnerability in the fine_vulture_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the security of the affected package but also pollutes the npm registry with potentially harmful variants. The origin of this vulnerability is traced back to a campaign that exploits npm's publishing mechanisms, leading to a significant risk of dependency confusion and supply chain attacks.

How To Fix

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

npm uninstall fine_vulture_0xrequest

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 fine_vulture_0xrequest package and replace it with a trusted alternative that provides similar functionality. Additionally, ensure that your package.json file does not include any references to this malicious package.

Conclusion

The fine_vulture_0xrequest package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package from your project and monitor for any similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for fine_vulture_0xrequest →

Share this vulnerability

FAQ

fine_vulture_0xrequest is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

This vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

If you have installed the fine_vulture_0xrequest package, it is crucial to uninstall it immediately to prevent any potential security risks.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing the package-lock.json file.

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall fine_vulture_0xrequest

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