Malicious Code Injection in tealove-darknest32 Package
Summary
MAL-2025-168289: Malicious code in tealove-darknest32 (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-darknest32 package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious packages flooding 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 for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.
Vulnerability Detail
The vulnerability in the tealove-darknest32 package originates from its inclusion in a campaign that utilizes autopublish scripts to manipulate package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-darknest32If 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, avoid using the tealove-darknest32 package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.
Conclusion
The tealove-darknest32 package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities.
See every vulnerability recorded for tealove-darknest32 →
FAQ
tealove-darknest32 is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
If you have installed tealove-darknest32, you should uninstall it immediately and check your project for any potential security issues.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider using other reputable packages that provide similar functionality without the associated risks of malicious code.
