Malicious Code Injection in tealoveness45: A Threat to npm Ecosystem
Summary
MAL-2025-168773: Malicious code in tealoveness45 (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 tealoveness45 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by creating and publishing numerous derivative packages. This behavior is primarily aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in tealoveness45 arises from the inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which floods the npm registry with these manipulated packages, potentially compromising the integrity of the ecosystem and affecting developers' projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness45If 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 prevent the installation of the tealoveness45 package by using npm's package-lock.json to monitor your dependencies. If you are using Vulert, you can check your application for vulnerabilities without any installation by visiting the Vulert playground at https://vulert.com/scanner.
Conclusion
The tealoveness45 package poses a significant threat to the npm ecosystem due to its malicious code that alters package configurations. Developers are advised to uninstall this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the security of your software.
See every vulnerability recorded for tealoveness45 →
FAQ
Tealoveness45 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the package immediately using the command 'npm uninstall tealoveness45' and check for any dependencies that may be affected.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
There is no patch for tealoveness45 as it is a malicious package. The best course of action is to remove it from your project.
