Malicious Code Vulnerability in increased_nightingale_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104075: Malicious code in increased_nightingale_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 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 increased_nightingale_0xrequest package is part of a broader campaign associated with the tea.xyz token reward system. This package, like many others in this campaign, is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. The primary functionality of this package is to facilitate the generation of these derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the increased_nightingale_0xrequest package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to flood npm with such malicious packages.

How To Fix

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

npm uninstall increased_nightingale_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 increased_nightingale_0xrequest 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 increased_nightingale_0xrequest package contains malicious code that poses a significant risk to projects using it. It is crucial to remove this package and replace it with a secure alternative to maintain the integrity of your software. Regular monitoring and auditing of your dependencies are essential to avoid similar vulnerabilities in the future.

See every vulnerability recorded for increased_nightingale_0xrequest →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign that generates and publishes derivative packages to manipulate npm registry reputation.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project and potentially introducing security risks.

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.

You should uninstall the package immediately and replace it with a secure alternative. Regularly audit your dependencies for vulnerabilities.

There is no patch for the increased_nightingale_0xrequest package; the recommended action is to remove it from your project.

How To Fix

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

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