Malicious Code Injection in tealove-nice50: A Threat to npm Users
Summary
MAL-2025-168531: Malicious code in tealove-nice50 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealove-nice50 is part of a broader campaign associated with the tea.xyz token reward initiative, 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 presence of such malicious code poses a significant risk to users who may unknowingly install these compromised packages, leading to potential security breaches and data integrity issues.
Vulnerability Detail
The vulnerability in tealove-nice50 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's package management system for malicious purposes. Users who install this package may inadvertently expose their systems to further attacks or data manipulation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice50If 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, users can avoid using the tealove-nice50 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, users can implement strict package management practices, such as using npm audit to identify and address vulnerabilities in their dependencies.
Conclusion
The tealove-nice50 package presents a significant security risk due to its malicious code designed to manipulate npm's package management system. Users are urged to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can help maintain the security of your projects by identifying vulnerabilities in real-time.
See every vulnerability recorded for tealove-nice50 →
FAQ
Tealove-nice50 is an npm package that has been identified as malicious, part of a campaign to manipulate developer reputation scores through the creation of numerous derivative packages.
Installing the tealove-nice50 package can lead to security breaches, data integrity issues, and the pollution of your project's dependency tree with malicious packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.
Immediately remove the tealove-nice50 package from your project and check for any other affected packages. Update your dependencies and run npm audit to identify any other vulnerabilities.
Yes, consider looking for other npm packages that offer similar functionality without the associated risks. Always verify the credibility of packages before installation.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
