Malicious Code Injection in tealove-nice36: A Threat to npm Ecosystem
Summary
MAL-2025-168515: Malicious code in tealove-nice36 (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-nice36 is part of a broader campaign targeting the npm ecosystem, associated with the tea.xyz token reward initiative. This package is designed to manipulate npm's publishing system, creating numerous derivative packages with randomized names. Its primary functionality revolves around inflating developer reputation scores through automated publishing scripts.
Vulnerability Detail
The vulnerability in tealove-nice36 stems from its malicious code, 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 the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-nice36If 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 the tealove-nice36 package by using npm's package-lock.json file to lock down your dependencies. This will help mitigate the risk of inadvertently installing this malicious package.
Conclusion
The tealove-nice36 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to uninstall the affected package and safeguard your projects.
See every vulnerability recorded for tealove-nice36 →
FAQ
The impact includes potential pollution of the npm registry, which can lead to compromised developer reputation and security risks for applications relying on affected packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.
There is no patch available for tealove-nice36 as it is a malicious package. The recommended action is to uninstall it and avoid using it in your projects.
If you have installed tealove-nice36, you should immediately uninstall it using the command: npm uninstall tealove-nice36.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the open-source community.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
