Malicious Code Injection in tealove-nameka33: A Threat to npm Ecosystem
Summary
MAL-2025-168416: Malicious code in tealove-nameka33 (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-nameka33 is part of a broader campaign associated with the tea.xyz token reward initiative, which has inundated the npm registry with numerous packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly incorporate these malicious packages into their projects.
Vulnerability Detail
The vulnerability in tealove-nameka33 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to compromised developer environments and potential exploitation of applications that rely on these packages, making it crucial for developers to be aware of and address this issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka33If 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-nameka33 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.
Conclusion
The tealove-nameka33 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. Developers must take immediate action to remove this package and monitor their dependencies for any signs of compromise. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for tealove-nameka33 →
FAQ
Tealove-nameka33 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 introduction of malicious code into your project, potentially compromising your application's security and integrity.
You should immediately uninstall the package using 'npm uninstall tealove-nameka33' and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner.
There are no patches available for tealove-nameka33 as it is a malicious package. The best course of action is to remove it from your project.
