Malicious Code Injection in bright_stingray_0xrequest: A Threat to npm Packages
Summary
MAL-2025-100110: Malicious code in bright_stingray_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package bright_stingray_0xrequest is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in bright_stingray_0xrequest originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This can result in a loss of integrity for the npm ecosystem, as it allows for the proliferation of potentially harmful packages that can be exploited by attackers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bright_stingray_0xrequestIf 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 bright_stingray_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The bright_stingray_0xrequest package poses a significant risk due to its malicious code that alters package metadata and proliferates harmful variants in the npm registry. It is crucial to remove this package from your projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of your applications.
See every vulnerability recorded for bright_stingray_0xrequest →
FAQ
bright_stingray_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.
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 using 'npm uninstall bright_stingray_0xrequest' and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
