Malicious Code Injection in tealoveness36 Package: A Threat to npm Users
Summary
MAL-2025-168763: Malicious code in tealoveness36 (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 tealoveness36 package 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 tealoveness36 is to facilitate this malicious activity, making it a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the tealoveness36 package originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload can inflate developer reputation scores fraudulently, undermining trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness36If 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 workaround, you can manually check your package-lock.json file for any references to tealoveness36 and remove it. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealoveness36 package poses a significant threat due to its malicious code designed to manipulate the npm registry. Users are advised to remove this package and utilize monitoring tools like Vulert to stay informed about vulnerabilities in their dependencies.
See every vulnerability recorded for tealoveness36 →
FAQ
Tealoveness36 is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
You should immediately remove the tealoveness36 package from your project and monitor your dependencies for any vulnerabilities.
Yes, you can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.
