Malicious Code Injection in underlying_stingray_z3n Package
Summary
MAL-2025-97114: Malicious code in underlying_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 underlying_stingray_z3n package 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, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the underlying_stingray_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, increased risk of dependency confusion attacks, and the undermining of developer trust in the npm ecosystem. The malicious payload is designed to exploit the npm registry's mechanisms for reputation and visibility.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall underlying_stingray_z3n
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 underlying_stingray_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time based on your package-lock.json file.
Conclusion
The underlying_stingray_z3n package contains malicious code that poses significant risks to applications using it. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for underlying_stingray_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code modifies your package.json, potentially leading to dependency confusion and pollution of the npm registry.
You should uninstall the underlying_stingray_z3n package immediately and check for any lingering references in your package-lock.json.
Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.