Malicious Code Injection in tealoveness21: A Threat to npm Ecosystem
Summary
MAL-2025-168747: Malicious code in tealoveness21 (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 tealoveness21 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to automate the generation and publication of derivative packages, which can mislead developers and inflate reputation scores for token rewards. This package, like others in the campaign, contains scripts that manipulate package metadata and continuously republish variants, contributing to registry pollution.
Vulnerability Detail
The vulnerability in tealoveness21 stems from its malicious payload that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the package management system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness21If 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 tealoveness21 package and monitor your dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The tealoveness21 package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and repopulates the registry with tainted variants. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking immediate action to remove affected packages is essential to maintaining project security.
See every vulnerability recorded for tealoveness21 →
FAQ
Tealoveness21 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publication.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealoveness21' and monitor your project for any unusual behavior.
Yes, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities.
You can find detailed information about this vulnerability in the Open Source Vulnerability database or by using monitoring tools like Vulert.
