Malicious Code Injection in tealove-nice10: A Threat to npm Ecosystem
Summary
MAL-2025-168487: Malicious code in tealove-nice10 (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 'tealove-nice10' is part of a larger campaign associated with the tea.xyz token reward initiative. It is 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, as it can lead to the proliferation of malicious packages that can compromise user systems.
Vulnerability Detail
The vulnerability in 'tealove-nice10' originates from its malicious payload, which 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 variants to clutter the npm registry. This not only affects the reputation of legitimate developers but also increases the risk of users inadvertently installing compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice10
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 measure, avoid using the 'tealove-nice10' package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your package-lock.json file to ensure no malicious packages are present.
Conclusion
The 'tealove-nice10' package poses a significant threat due to its malicious code that modifies package metadata and proliferates compromised packages in the npm ecosystem. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for tealove-nice10 →
FAQ
The primary risk is the potential for malicious code execution and the pollution of the npm registry with compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package using 'npm uninstall tealove-nice10' and check for any dependencies that may have included it.
As of now, there are no known patches for 'tealove-nice10'. It is recommended to remove the package entirely.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.