Malicious Code Injection in tealove-nameka12: A Threat to npm Packages
Summary
MAL-2025-168393: Malicious code in tealove-nameka12 (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-nameka12 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 the automatic generation and publishing of derivative packages. The malicious behavior includes modifying package.json files to remove private flags, changing version numbers, and creating random package names, which can lead to pollution of the npm registry.
Vulnerability Detail
The vulnerability in tealove-nameka12 originates from its involvement in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages. The payload modifies critical files, potentially leading to security breaches and the spread of further malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka12If 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-nameka12 package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The tealove-nameka12 package poses significant risks due to its malicious code designed to manipulate npm packages. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can safeguard your projects from potential threats.
See every vulnerability recorded for tealove-nameka12 →
FAQ
tealove-nameka12 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 malicious code that modifies your package.json file, potentially compromising your project's security and integrity.
You should uninstall the package immediately using the command 'npm uninstall tealove-nameka12' and review your project for any other potentially harmful packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other reputable packages that offer similar functionalities without the risks associated with tealove-nameka12.
