Malicious Code Injection in tealove-naiman40: A Threat to npm Ecosystem
Summary
MAL-2025-168379: Malicious code in tealove-naiman40 (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-naiman40 is part of a broader campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in tealove-naiman40 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. These modifications remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly integrate these compromised packages into their projects, as well as a degradation of the overall integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-naiman40If 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-naiman40 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The tealove-naiman40 package poses a significant threat due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package from their projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their dependencies.
See every vulnerability recorded for tealove-naiman40 →
FAQ
Tealove-naiman40 is an npm package involved in a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of compromised packages in your project, posing security risks and potentially affecting the integrity of your application.
You should uninstall the package immediately using 'npm uninstall tealove-naiman40' and check your package-lock.json for any references to it.
Yes, tools like Vulert can help monitor your dependencies for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
