Malicious Code Injection in tealove-nameka44: A Threat to npm Ecosystem
Summary
MAL-2025-168428: Malicious code in tealove-nameka44 (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-nameka44 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 not only clutters the npm registry but also poses a significant risk to developers who may unknowingly install these malicious packages.
Vulnerability Detail
The vulnerability in tealove-nameka44 stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The origin of this issue is linked to a broader campaign aimed at exploiting the npm ecosystem for token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nameka44If 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 prevent the installation of this package by using npm's package-lock.json to monitor and restrict the use of vulnerable packages. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealove-nameka44 package presents a significant security risk due to its malicious behavior of modifying package configurations and republishing variants. Developers are advised to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure ongoing security.
See every vulnerability recorded for tealove-nameka44 →
FAQ
Tealove-nameka44 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, which may compromise your project's integrity and security by modifying package configurations and republishing variants.
You should immediately remove the tealove-nameka44 package from your project and check for any other affected packages. Use the command 'npm uninstall tealove-nameka44' to remove it.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay updated on security advisories related to your packages.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
