Malicious Code Injection in tealove-nameka10: A Threat to npm Packages
Summary
MAL-2025-168391: Malicious code in tealove-nameka10 (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-nameka10 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through automated scripts that publish numerous derivative packages with randomized names. The presence of such packages poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in tealove-nameka10 arises from its malicious payload 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, which pollutes the npm registry and can compromise the integrity of the software supply chain. The origin of this vulnerability is linked to the broader tea.xyz token reward campaign, which employs these tactics to manipulate npm's reputation system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka10If 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 the tealove-nameka10 package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package management practices, such as using npm audit to identify vulnerabilities in your dependencies.
Conclusion
The tealove-nameka10 package poses a significant security risk due to its malicious behavior of modifying package metadata and republishing variants. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your project's security posture.
See every vulnerability recorded for tealove-nameka10 →
FAQ
tealove-nameka10 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and exposing it to further security risks.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected by this vulnerability.
If you have installed tealove-nameka10, it is recommended to remove it immediately and check for any other affected packages in your project.
Yes, tools like Vulert can help monitor your project for vulnerabilities in real-time using just the package-lock.json file, without requiring code access or installation.
