Malicious Code Injection in tealoveness69: A Threat to npm Ecosystem
Summary
MAL-2025-168799: Malicious code in tealoveness69 (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 package tealoveness69 is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealoveness69 is compromised by its malicious intent, which includes modifying package metadata and republishing variants to clutter the npm registry.
Vulnerability Detail
The vulnerability in tealoveness69 originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to significant pollution of the npm registry. The ramifications include potential security risks for developers who unknowingly install these packages, as they may inadvertently contribute to the proliferation of malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness69If 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 avoid using tealoveness69 and any other packages associated with the tea.xyz campaign. Monitor your package dependencies and consider using tools like Vulert to identify and alert you about vulnerabilities in your software.
Conclusion
The tealoveness69 package poses a significant threat to the npm ecosystem due to its malicious design aimed at manipulating package metadata and flooding the registry with unwanted variants. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for tealoveness69 →
FAQ
Tealoveness69 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious packages that may compromise your project's security and contribute to the pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall tealoveness69' and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities 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 needing to sign up.
