Malicious Code Exploit in tealove-naiman33 Package: npm Vulnerability Summary
Summary
MAL-2025-168372: Malicious code in tealove-naiman33 (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 tealove-naiman33 package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores in exchange for tea protocol token rewards. Its functionality is primarily centered around manipulating npm registry entries, which poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the tealove-naiman33 package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious scripts included in this package (auto.js, autopublish.js, etc.) are designed to automate these harmful actions, making it a significant threat to the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-naiman33If 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 workaround, you can use the following command to uninstall the affected package: npm uninstall tealove-naiman33. Additionally, consider using Vulert to monitor your project for vulnerabilities. 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-naiman33 package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove this package from their projects to maintain the integrity of their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.
See every vulnerability recorded for tealove-naiman33 →
FAQ
The tealove-naiman33 package is part of a malicious campaign that automates the generation of npm packages to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project and potentially introducing other malicious packages.
You should uninstall the tealove-naiman33 package immediately to prevent any potential risks to your project.
Currently, there is no patch available for the tealove-naiman33 package. The best course of action is to uninstall it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit https://vulert.com for more information.
