Malicious Code Injection in tealoveness4 Package - npm Vulnerability
Summary
MAL-2025-168767: Malicious code in tealoveness4 (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 tealoveness4 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that manipulate package metadata and continuously republish variants to the npm registry, posing a significant risk to developers and users alike.
Vulnerability Detail
The vulnerability in the tealoveness4 package stems from its malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the developer's environment, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness4If 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 tealoveness4 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your package-lock.json file to ensure no malicious packages are present.
Conclusion
The tealoveness4 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for tealoveness4 →
FAQ
Tealoveness4 is an npm package associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the injection of malicious code into your project, compromising its integrity and potentially leading to security breaches.
You should uninstall the tealoveness4 package immediately using the command: npm uninstall tealoveness4.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, there are multiple packages associated with the tea.xyz token reward campaign that may exhibit similar malicious behavior. It is advisable to audit your dependencies regularly.
