Malicious Code Vulnerability in tealoveness49: npm Package Compromised
Summary
MAL-2025-168777: Malicious code in tealoveness49 (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 tealoveness49 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in tealoveness49 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior can compromise the security of applications using this package, potentially introducing malicious code into production environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness49If 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 tealoveness49 package and replace it with a trusted alternative that provides similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The tealoveness49 package poses a significant security risk due to its malicious code that alters package configurations and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies to maintain application security.
See every vulnerability recorded for tealoveness49 →
FAQ
Tealoveness49 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can help you identify if your application is affected by the tealoveness49 vulnerability.
Using compromised packages can lead to the introduction of malicious code into your application, potentially resulting in data breaches, unauthorized access, and other security incidents.
To prevent vulnerabilities, regularly audit your dependencies, use tools like npm audit, and consider employing automated monitoring solutions like Vulert to stay informed about potential risks.
If you have used tealoveness49, immediately uninstall the package and review your code for any potential impacts. Replace it with a trusted alternative and ensure your application is secure.
