Malicious Code Injection in tealove-nice34: A Threat to npm Users
Summary
MAL-2025-168513: Malicious code in tealove-nice34 (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-nice34 is part of a broader campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores through automated scripts that publish numerous derivative packages with altered names and metadata. The malicious nature of tealove-nice34 poses significant risks to developers who may unknowingly integrate it into their projects.
Vulnerability Detail
The vulnerability in tealove-nice34 originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for projects that depend on this package, and the manipulation of developer reputation scores. The malicious payload can compromise the integrity of applications relying on affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice34If 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 avoid using tealove-nice34 and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes that may indicate the presence of malicious packages.
Conclusion
The tealove-nice34 package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is essential to remove this package from your projects and monitor for any vulnerabilities using tools like Vulert to ensure the security of your applications.
See every vulnerability recorded for tealove-nice34 →
FAQ
Tealove-nice34 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potential security risks, and the compromise of the integrity of applications that depend on the affected package.
If you have installed tealove-nice34, it is crucial to remove it from your project immediately and monitor for any unauthorized changes in your package-lock.json file.
Yes, you can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software by analyzing your 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.
