Malicious Code Injection in tealoveness41: A Threat to npm Packages
Summary
MAL-2025-168769: Malicious code in tealoveness41 (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 tealoveness41 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages. This behavior not only compromises the integrity of the npm registry but also poses a significant risk to developers who may unknowingly use these malicious packages.
Vulnerability Detail
The vulnerability in tealoveness41 originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior can lead to the proliferation of insecure packages, potentially allowing attackers to exploit unsuspecting developers and users.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness41If 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 tealoveness41 package entirely and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The tealoveness41 package poses a significant threat due to its malicious code designed to manipulate npm's registry. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for tealoveness41 →
FAQ
Tealoveness41 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the introduction of insecure packages into your project, which may compromise its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealoveness41' and check for any other affected packages in your project.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, you should look for reputable packages that offer similar functionality without the risks associated with tealoveness41.
