Malicious Code Injection in tealove-nameka2: A Threat to npm Users
Summary
MAL-2025-168401: Malicious code in tealove-nameka2 (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
tealove-nameka2 is an npm package that is part of a broader campaign associated with the tea.xyz token reward system. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in tealove-nameka2 stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka2If 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, users can avoid using the tealove-nameka2 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages for vulnerabilities using tools like npm audit.
Conclusion
The tealove-nameka2 package poses a significant risk due to its malicious behavior, which can compromise the integrity of projects using it. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tealove-nameka2 →
FAQ
tealove-nameka2 is an npm package involved in a malicious campaign that generates and publishes derivative packages to manipulate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your project, potentially compromising security and functionality.
You should remove the package immediately and monitor your project for any unusual behavior or security issues.
Yes, tools like npm audit can help identify vulnerabilities. Additionally, you can use Vulert to monitor and alert for open-source vulnerabilities in real-time.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
