Malicious Code Injection in nasty_bird_0xrequest Package: A Threat to npm Users

nasty_bird_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106185: Malicious code in nasty_bird_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 nasty_bird_0xrequest package is part of a series of malicious packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. The primary functionality of these packages is to inflate developer reputation scores for token rewards, but they pose significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

This vulnerability originates from the malicious design of the nasty_bird_0xrequest package, which includes scripts that modify the package.json file to remove private flags and alter version numbers. The package generates random names for derivative packages and continuously republishes them, leading to pollution of the npm registry. This can result in compromised applications, as developers may unknowingly install these malicious packages, exposing their projects to security risks and potential data breaches.

How To Fix

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

npm uninstall nasty_bird_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 nasty_bird_0xrequest package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The nasty_bird_0xrequest package poses a significant threat to npm users due to its malicious design aimed at manipulating the npm registry. It is essential to remove this package and monitor your dependencies for vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for nasty_bird_0xrequest →

Share this vulnerability

FAQ

The nasty_bird_0xrequest package is a malicious npm package designed to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the installation of malicious packages, compromising your application's security and potentially exposing sensitive data.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately remove the nasty_bird_0xrequest package from your project and check for any other affected dependencies.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your project's dependencies.

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 nasty_bird_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