Malicious Code Vulnerability in various_stingray-appteadev Package
Summary
MAL-2025-110360: Malicious code in various_stingray-appteadev (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 various_stingray-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the development of applications by providing various utilities. However, it has been compromised, leading to significant security concerns due to its malicious behavior.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall various_stingray-appteadevIf 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 remove the package from your project by executing: npm uninstall various_stingray-appteadev. This will prevent any malicious code from executing in your application.
Conclusion
The various_stingray-appteadev package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for various_stingray-appteadev →
FAQ
The malicious code modifies package.json to remove private flags and generates random package names, contributing to the pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Using the compromised package can lead to the installation of malicious derivatives, which may compromise your application’s security and integrity.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
If you cannot update or remove the package, consider isolating its usage and monitoring your application closely for any unusual behavior.
