Malicious Code Injection in ambitious_vulture_0xrequest Package

ambitious_vulture_0xrequest Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99397: Malicious code in ambitious_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 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 ambitious_vulture_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publishing of derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. However, this functionality has led to the introduction of malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the ambitious_vulture_0xrequest package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly integrate these packages into their projects. The malicious payload can also affect the reputation of legitimate developers by flooding the registry with spammy packages.

How To Fix

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

npm uninstall ambitious_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 ambitious_vulture_0xrequest package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The ambitious_vulture_0xrequest package contains malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package and regularly audit their dependencies to maintain the security of their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for ambitious_vulture_0xrequest →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, affecting the integrity of package management and potentially compromising the security of applications that depend on these packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed the ambitious_vulture_0xrequest package, you should uninstall it immediately and check your project for any other potentially malicious packages.

Currently, there are no known patches for the ambitious_vulture_0xrequest package. The best course of action is to remove the package entirely.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using packages from untrusted sources.

How To Fix

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

npm uninstall ambitious_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