Malicious Code Vulnerability in tealove-nameka4: A Threat to npm Packages
Summary
MAL-2025-168423: Malicious code in tealove-nameka4 (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-nameka4 is part of a broader campaign associated with the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, which poses a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-nameka4 stems from its inclusion in a malicious campaign 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 these variants, effectively polluting the npm registry. The malicious payload can compromise the security of applications relying on this package, potentially leading to unauthorized access or exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka4If 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-nameka4 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The tealove-nameka4 package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. It is essential to remove this package from your projects and remain vigilant about the security of your dependencies. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities.
See every vulnerability recorded for tealove-nameka4 →
FAQ
Tealove-nameka4 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 inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command 'npm uninstall tealove-nameka4' and review your dependencies for any other malicious packages.
Regularly audit your dependencies, use trusted packages, and leverage tools like Vulert to monitor for vulnerabilities in real-time.
Vulert is a tool that monitors your package-lock.json for open-source vulnerabilities in real-time. You can use the Vulert playground to check if your application is affected by this vulnerability without needing to sign up.
