Malicious Code Injection in tealoveness30: A Threat to npm Ecosystem
Summary
MAL-2025-168757: Malicious code in tealoveness30 (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 tealoveness30 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. This package, like others in its category, is characterized by its use of autopublish scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in tealoveness30 arises from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness30If 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 tealoveness30 package and any packages that depend on it. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The tealoveness30 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove any instances of this package from their projects to mitigate potential risks. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for tealoveness30 →
FAQ
Tealoveness30 is an npm package that is part of a token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the pollution of the npm registry and may expose your project to security risks if compromised packages are inadvertently used.
You should uninstall the package immediately using 'npm uninstall tealoveness30' and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
