Malicious Code Injection in tealoveness34: A Threat to npm Ecosystem
Summary
MAL-2025-168761: Malicious code in tealoveness34 (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 tealoveness34 is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of tealoveness34 is to serve as a vehicle for these malicious activities, posing a significant risk to developers and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in tealoveness34 originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications of this vulnerability include compromised developer reputations, potential security risks for applications using these packages, and overall degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness34If 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 tealoveness34 package and monitor your project for any instances of its usage. Additionally, consider using tools like Vulert to scan your package-lock.json for vulnerabilities. You can access Vulert's playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.
Conclusion
The tealoveness34 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for tealoveness34 →
FAQ
Tealoveness34 is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially exposing it to security risks.
You should remove the tealoveness34 package from your project and monitor for any instances of its usage to prevent potential security issues.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by vulnerabilities without needing to sign up.
