Malicious Code Injection in tealove-nameka43: A Threat to npm Ecosystem
Summary
MAL-2025-168427: Malicious code in tealove-nameka43 (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-nameka43 is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses significant risks to the integrity of the npm registry and can lead to the proliferation of malicious software.
Vulnerability Detail
The vulnerability in tealove-nameka43 originates from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages and applications that depend on it. The malicious scripts included in the package are designed to automate this process, making it difficult for developers to detect and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka43If 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-nameka43 package and replace it with a reputable alternative that serves the same purpose without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The tealove-nameka43 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Taking proactive measures can help safeguard applications against such threats.
See every vulnerability recorded for tealove-nameka43 →
FAQ
Tealove-nameka43 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, potentially compromising your application by introducing malicious code through derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
You should immediately uninstall the package using the command 'npm uninstall tealove-nameka43' and review your project for any other potentially malicious packages.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities using just your package-lock.json file, providing real-time alerts.
