Malicious Code Injection in tealove-nokire35: A Threat to npm Users
Summary
MAL-2025-168564: Malicious code in tealove-nokire35 (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-nokire35 is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify essential files, such as package.json, thereby compromising the integrity of the projects that depend on it.
Vulnerability Detail
The vulnerability in tealove-nokire35 originates from its design to include autopublish scripts that remove private flags from package.json, change version numbers, and generate random package names. This behavior not only pollutes the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of control over their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nokire35If 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-nokire35 package and look for alternative packages that provide similar functionality without the associated risks. 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-nokire35 package poses a significant threat to npm users due to its malicious code that modifies essential project files. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from such threats.
See every vulnerability recorded for tealove-nokire35 →
FAQ
tealove-nokire35 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 modification of your package.json file, potentially exposing your project to security risks and causing issues with package management.
You should uninstall the package immediately using the command npm uninstall tealove-nokire35 and check your project files for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.
