Malicious Code Injection in tealove-nice39: A Threat to npm Users
Summary
MAL-2025-168518: Malicious code in tealove-nice39 (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-nice39 is part of a larger campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary function of these packages is to exploit the npm registry for token rewards, making them a significant threat to developers and users relying on npm for package management.
Vulnerability Detail
The vulnerability in tealove-nice39 originates from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The malicious payload poses risks such as unauthorized access to sensitive data, potential exploitation of other dependencies, and a general degradation 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 tealove-nice39If 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, you can avoid using the tealove-nice39 package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The tealove-nice39 package poses a significant threat to npm users due to its malicious code designed to manipulate package management for token rewards. It is essential to uninstall this package and monitor your project for vulnerabilities using tools like Vulert. Always prioritize the security of your dependencies to maintain the integrity of your software.
See every vulnerability recorded for tealove-nice39 →
FAQ
Tealove-nice39 is an npm package that has been identified as malicious, part of a campaign to exploit the npm registry for token rewards.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's integrity and security.
You should uninstall the package immediately using the command 'npm uninstall tealove-nice39' and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider researching and using alternative packages that provide similar functionality but have a verified reputation and no known vulnerabilities.
