Malicious Code Injection in tealoveness13: A Threat to npm Users
Summary
MAL-2025-168738: Malicious code in tealoveness13 (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 tealoveness13 is part of the tea.xyz token reward campaign, which has been identified as a source of malicious activity within the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is primarily centered around manipulating the npm registry, making it a significant concern for developers using npm packages.
Vulnerability Detail
The vulnerability in tealoveness13 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses risks of dependency confusion and potential exploitation by other malicious actors. The package continuously republishes variants, leading to pollution of the npm registry and undermining the trustworthiness of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness13If 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 tealoveness13 package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The tealoveness13 package poses a significant threat to npm users due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for security vulnerabilities.
See every vulnerability recorded for tealoveness13 →
FAQ
Tealoveness13 is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of modifying package metadata and republishing variants.
The vulnerability can lead to the pollution of the npm registry, potential dependency confusion, and may expose your project to further malicious activities.
You should uninstall the package immediately using 'npm uninstall tealoveness13' and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground without any signup.
No patches are available for tealoveness13 as it is a malicious package. The best course of action is to remove it from your project.
