Malicious Code Injection in open_stingray_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95754: Malicious code in open_stingray_z3n (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 open_stingray_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by generating and publishing derivative packages with randomized names. The malicious behavior is primarily driven by the tea.xyz token reward campaign, which incentivizes developers to inflate their reputation scores through automated scripts.
Vulnerability Detail
The vulnerability in open_stingray_z3n originates from its association with the tea.xyz token reward campaign. It includes malicious payloads that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The impact of this vulnerability includes potential reputation damage for developers and increased difficulty in managing legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall open_stingray_z3nIf 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 measure, you can avoid using the open_stingray_z3n package and any other packages that may be part of the tea.xyz campaign. Monitor your package.json file for any unauthorized changes and revert them if necessary.
Conclusion
The open_stingray_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can help protect your projects from potential exploitation.
See every vulnerability recorded for open_stingray_z3n →
FAQ
open_stingray_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies.
You should uninstall the open_stingray_z3n package immediately and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
