Malicious Code Injection in tealoveness18 Package - npm Vulnerability
Summary
MAL-2025-168743: Malicious code in tealoveness18 (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 tealoveness18 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the tealoveness18 package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages and applications that depend on it. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate this malicious behavior.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness18
If 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 remove the tealoveness18 package from your project by executing the command: 'npm uninstall tealoveness18'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The tealoveness18 package presents a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is crucial to take immediate action by uninstalling the package and monitoring your application for vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealoveness18 →
FAQ
Tealoveness18 is an npm package that is part of a token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the modification of your package.json file, potentially compromising the integrity of your application and its dependencies.
You should uninstall the package immediately and check for any other affected packages in your application.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.