Malicious Code Injection in tealoveness6: A Threat to npm Packages
Summary
MAL-2025-168789: Malicious code in tealoveness6 (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
tealoveness6 is a package that 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 for token rewards by automatically generating and publishing derivative packages with randomized names. The primary functionality of tealoveness6 is to serve as a tool within this campaign, but its malicious behavior poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealoveness6 originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may introduce malicious code into their projects, compromise their systems, and damage their reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness6If 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 workaround, you can avoid using the tealoveness6 package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json file for vulnerabilities in real-time.
Conclusion
The tealoveness6 package poses a significant threat due to its malicious code that modifies package.json and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities. Staying informed and proactive can help maintain the integrity of your software.
See every vulnerability recorded for tealoveness6 →
FAQ
tealoveness6 is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.
The vulnerability can lead to the introduction of malicious code into your project, compromising security and potentially damaging your reputation.
You should uninstall the tealoveness6 package immediately using 'npm uninstall tealoveness6' and consider using alternative packages.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
