Malicious Code Injection in tealoveness55: A Threat to npm Packages
Summary
MAL-2025-168784: Malicious code in tealoveness55 (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 tealoveness55 is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm ecosystem by automatically generating and publishing derivative packages. It aims to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability in tealoveness55 originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, ultimately polluting the npm registry and potentially compromising the integrity of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness55If 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 measure, you can avoid using the tealoveness55 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The tealoveness55 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to ensure the security of their applications.
See every vulnerability recorded for tealoveness55 →
FAQ
Tealoveness55 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 pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the package immediately using 'npm uninstall tealoveness55' and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
