Malicious Code Injection in tealove-nice41: A Threat to npm Users
Summary
MAL-2025-168521: Malicious code in tealove-nice41 (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-nice41 is part of a broader campaign targeting npm users, associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in tealove-nice41 stems 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, polluting the npm registry and potentially compromising the integrity of projects that depend on these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which employs such tactics to exploit npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice41If 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 prevent the installation of this malicious package by using npm's package-lock.json file to monitor your dependencies. You can also utilize tools like Vulert to check for vulnerabilities in your application without requiring code access. For instance, you can visit the Vulert playground at https://vulert.com/scanner to assess if your application is affected by this vulnerability.
Conclusion
The tealove-nice41 package poses a significant risk to npm users due to its malicious code designed to manipulate the npm registry. It is essential to uninstall this package and monitor your dependencies for vulnerabilities using tools like Vulert to maintain the integrity of your projects.
See every vulnerability recorded for tealove-nice41 →
FAQ
tealove-nice41 is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project by introducing untrusted packages.
You should uninstall the package immediately using the command 'npm uninstall tealove-nice41' and review your project's dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
