Malicious Code Vulnerability in tealoveness25: Exploitation of npm Packages for Token Rewards
Summary
MAL-2025-168751: Malicious code in tealoveness25 (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 tealoveness25 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to interact with the npm ecosystem, allowing developers to publish and manage JavaScript packages. However, this package has been identified as malicious, containing scripts that automate the generation and publication of derivative packages, which can lead to reputation inflation and registry pollution.
Vulnerability Detail
The vulnerability in tealoveness25 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts (auto.js, autopublish.js, etc.) that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness25If 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 monitor your dependencies using tools like Vulert, which allows you to check for vulnerabilities without requiring code access or installation. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.
Conclusion
The tealoveness25 package poses a significant risk due to its malicious nature and exploitation of the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for potential vulnerabilities in their dependencies.
See every vulnerability recorded for tealoveness25 →
FAQ
Tealoveness25 is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry for token rewards.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies, potentially introducing security risks.
You should uninstall the package immediately using the command npm uninstall tealoveness25 and check your project for any references to it.
Currently, there is no patched version of tealoveness25 available, so the only course of action is to remove the package.
You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
