Malicious Code Injection in tealove-nameka41: A Threat to npm Packages
Summary
MAL-2025-168425: Malicious code in tealove-nameka41 (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-nameka41 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 manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of these packages is to inflate the visibility and reputation of the tea protocol, but they come with significant risks due to their malicious payloads.
Vulnerability Detail
The vulnerability in tealove-nameka41 arises from its inclusion in a campaign that utilizes autopublish scripts to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious behavior can compromise the integrity of the npm ecosystem, potentially affecting other packages and developers relying on npm for their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka41If 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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include tealove-nameka41 in your package.json or lock file.
Conclusion
The tealove-nameka41 package poses a significant risk due to its malicious code that modifies package.json files and pollutes the npm registry. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealove-nameka41 →
FAQ
Tealove-nameka41 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting the overall security of your application.
You should remove the package from your project immediately and monitor for any updates or patches that may address this vulnerability.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application against vulnerabilities using the Vulert playground without any signup.
Currently, there is no specific patched version available for tealove-nameka41. It is advisable to remove the package until a secure version is released.
