Malicious Code Injection in qvibtt-devapptea: A Threat to npm Ecosystem
Summary
MAL-2025-107679: Malicious code in qvibtt-devapptea (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 qvibtt-devapptea is part of the tea.xyz token reward campaign, which has been associated with a series of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package poses a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in qvibtt-devapptea originates from its design to include autopublish scripts that modify package.json files. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also compromises the security of applications that depend on this package, potentially allowing for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall qvibtt-devappteaIf 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, consider removing the qvibtt-devapptea package from your project until a secure version is released. You can do this by executing: npm uninstall qvibtt-devapptea. Additionally, monitor your package-lock.json file for any unexpected changes.
Conclusion
The qvibtt-devapptea package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. Developers are urged to take immediate action by uninstalling the package and monitoring their applications for any vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts.
See every vulnerability recorded for qvibtt-devapptea →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants, compromising the integrity of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed qvibtt-devapptea, it is recommended to uninstall it immediately and check for any changes in your package-lock.json file.
Currently, there is no specific patched version available for qvibtt-devapptea. It is advisable to stay updated with the package repository for any future releases.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your applications remain secure.
