Malicious Code Injection in tealove-nice32 Package
Summary
MAL-2025-168511: Malicious code in tealove-nice32 (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 tealove-nice32 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages. The malicious nature of tealove-nice32 lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in the tealove-nice32 package originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to potential reputation damage for developers and pollution of the npm registry. The continuous republishing of these variants can also lead to security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice32If 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 avoid using the tealove-nice32 package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a safer alternative. You can remove the package using the following command: npm uninstall tealove-nice32.
Conclusion
The tealove-nice32 package poses a significant risk due to its malicious code that modifies critical files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for tealove-nice32 →
FAQ
Tealove-nice32 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 pollution of the npm registry and potential security risks for applications that depend on the compromised package.
You should uninstall the tealove-nice32 package immediately and check for any safer alternatives.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
