Malicious Code Injection in tealove-nice35: A Threat to npm Ecosystem
Summary
MAL-2025-168514: Malicious code in tealove-nice35 (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-nice35 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards related to the tea protocol. The package's functionality is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in tealove-nice35 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the integrity of the packages, potentially leading to security risks for users who unknowingly install these malicious versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice35If 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 tealove-nice35 and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your package dependencies for any malicious activity and consider using tools like Vulert to keep track of vulnerabilities in your project.
Conclusion
The tealove-nice35 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for tealove-nice35 →
FAQ
tealove-nice35 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.
The vulnerability can lead to the installation of malicious packages that compromise your project's security and integrity, potentially exposing sensitive data or introducing further vulnerabilities.
You should immediately uninstall tealove-nice35 using the command npm uninstall tealove-nice35 and review your project for any other potentially malicious packages.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file, providing alerts for any issues detected.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
