Malicious Code Injection in tealove-darknest6 Package
Summary
MAL-2025-168310: Malicious code in tealove-darknest6 (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-darknest6 package is part of a broader campaign associated with the tea.xyz token reward system, which has been flooding the npm registry. This package is designed to facilitate the automatic generation and publication of derivative packages. It aims to inflate developer reputation scores in exchange for tea protocol token rewards. However, its malicious nature poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the tealove-darknest6 package originates from its malicious payload, 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, effectively polluting the npm registry. The ramifications include compromised developer environments, potential security breaches, and a degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-darknest6If 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 remove the tealove-darknest6 package from your project to mitigate the risk. Use the following command to uninstall it: npm uninstall tealove-darknest6. Additionally, consider using alternative packages that do not exhibit malicious behavior.
Conclusion
The tealove-darknest6 package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to take immediate action by updating or removing the package to protect their projects and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for tealove-darknest6 →
FAQ
The tealove-darknest6 package is part of a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The vulnerability can compromise your project's integrity by modifying package files and introducing potentially harmful code.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
If you cannot update the package right away, consider removing it from your project as a temporary workaround to mitigate risks.
More information can be found in the vulnerability report on the GitHub repository for malicious packages or through security advisories related to npm.
