Malicious Code Injection in tealove-nameka39: A Threat to npm Packages
Summary
MAL-2025-168422: Malicious code in tealove-nameka39 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealove-nameka39 is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate 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 risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in tealove-nameka39 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to security risks for developers who rely on these packages. The autopublish scripts included in the package are specifically designed to automate this process, making it difficult for users to detect the malicious activity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka39If 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-nameka39 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unexpected changes in the package.json file.
Conclusion
The tealove-nameka39 package poses a significant threat due to its malicious behavior aimed at inflating developer reputation scores through the npm registry. It is crucial for developers to be aware of such vulnerabilities and take immediate action to protect their projects by removing the affected package and monitoring for any unusual changes.
See every vulnerability recorded for tealove-nameka39 →
FAQ
tealove-nameka39 is an npm package associated with the tea.xyz token reward campaign, which has been identified as malicious.
The vulnerability can lead to the automatic generation of malicious packages, which may compromise the integrity of your project and clutter the npm registry.
You should uninstall the package immediately using npm uninstall tealove-nameka39 and monitor your project for any unusual activity.
Yes, tools like Vulert can help monitor and alert you in real-time for open-source vulnerabilities in your software without requiring access to the code. You can check your application against known vulnerabilities using the Vulert playground.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
