Malicious Code Injection in tealove-naiman27 Package
Summary
MAL-2025-168366: Malicious code in tealove-naiman27 (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-naiman27 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of these packages is primarily malicious, aimed at inflating token rewards rather than providing legitimate utility.
Vulnerability Detail
The vulnerability in the tealove-naiman27 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for dependency confusion attacks and the compromise of developer environments.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-naiman27If 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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using tools like 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-naiman27 package poses a significant security risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for tealove-naiman27 →
FAQ
The tealove-naiman27 package is part of a malicious campaign that floods the npm registry with packages designed to inflate developer reputation scores for token rewards.
This vulnerability can lead to security risks such as dependency confusion and the potential compromise of your development environment.
You should uninstall the tealove-naiman27 package immediately and check your package-lock.json for any references to it.
Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
