Malicious Code Injection in tealove-nameka16: A Threat to npm Users
Summary
MAL-2025-168397: Malicious code in tealove-nameka16 (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-nameka16 is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to users who may inadvertently install these compromised packages.
Vulnerability Detail
The vulnerability in tealove-nameka16 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 pollute the npm registry and can lead to the installation of compromised packages by unsuspecting developers. The origin of this issue is linked to a broader campaign that exploits npm's package management system, making it crucial for developers to be vigilant about the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka16If 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-nameka16 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall tealove-nameka16.
Conclusion
The tealove-nameka16 package poses a significant risk due to its malicious code designed to manipulate npm's package management system. Developers should take immediate action to remove this package and consider using tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tealove-nameka16 →
FAQ
tealove-nameka16 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability to your project.
You should immediately uninstall the package using the command 'npm uninstall tealove-nameka16' and monitor your project for any unusual behavior.
Yes, you can use 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.
