Malicious Code Injection in tealove-nokire2: A Threat to npm Packages
Summary
MAL-2025-168547: Malicious code in tealove-nokire2 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealove-nokire2 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 manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in tealove-nokire2 stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. The ramifications of this vulnerability include potential exposure to malicious code, compromised application integrity, and the risk of developers inadvertently using these tainted packages in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nokire2If 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 avoid using the tealove-nokire2 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before including them in your project.
Conclusion
The tealove-nokire2 package poses a significant risk due to its malicious nature, which can compromise the integrity of applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for tealove-nokire2 →
FAQ
Tealove-nokire2 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command 'npm uninstall tealove-nokire2' and review your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality but are verified and trusted within the npm ecosystem.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
