Malicious Code Injection in tealoveness3: A Threat to npm Users
Summary
MAL-2025-168756: Malicious code in tealoveness3 (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 tealoveness3 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 malicious nature of tealoveness3 poses a significant risk to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in tealoveness3 originates from its inclusion in a campaign that uses autopublish scripts to modify package.json files. This manipulation removes private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for applications using these packages, as they may inadvertently include malicious code or dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness3If 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 tealoveness3 package and monitor your package-lock.json for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The tealoveness3 package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for tealoveness3 →
FAQ
Tealoveness3 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should remove the tealoveness3 package from your project and monitor your dependencies for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
