Malicious Code Injection in tealoveness37: A Threat to npm Packages
Summary
MAL-2025-168764: Malicious code in tealoveness37 (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 tealoveness37 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for rewards. This malicious behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on affected packages.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the tealoveness37 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for applications using these packages, and the undermining of developer reputation systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness37If 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 tealoveness37 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages to identify and remove any suspicious or untrusted packages.
Conclusion
The tealoveness37 package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and repopulates the registry with untrustworthy packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tealoveness37 →
FAQ
Tealoveness37 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks into your application if it relies on affected packages.
You should uninstall the tealoveness37 package immediately using 'npm uninstall tealoveness37' and audit your project for any other suspicious packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
