Malicious Code Injection in stingy_stingray_0xrequest Package

stingy_stingray_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109145: Malicious code in stingy_stingray_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 stingy_stingray_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 generation and publication of derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The functionality of this package is compromised due to the presence of malicious code that alters package metadata.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the package, which modifies the package.json file to remove private flags and changes version numbers. It also generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion and the spread of malicious code across projects that rely on this package.

How To Fix

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

npm uninstall stingy_stingray_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 manually inspect your package.json file and remove any references to the stingy_stingray_0xrequest package. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The stingy_stingray_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package from your project and monitor your dependencies regularly to maintain security.

See every vulnerability recorded for stingy_stingray_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

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

You should uninstall the package immediately and check your project for any unintended changes made by the malicious code.

Yes, regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert to monitor for vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

How To Fix

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

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