Malicious Code Injection in tealoveness52: A Threat to npm Packages
Summary
MAL-2025-168781: Malicious code in tealoveness52 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealoveness52 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate token rewards through the automatic generation and publication of derivative packages. This package, like others in the campaign, is equipped with scripts that manipulate package metadata to enhance developer reputation scores fraudulently.
Vulnerability Detail
The vulnerability in tealoveness52 stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealoveness52If 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 avoid using the tealoveness52 package altogether. If it is already in use, consider replacing it with a reputable alternative that does not have known vulnerabilities. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The tealoveness52 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is essential for developers to be vigilant, remove this package, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.
See every vulnerability recorded for tealoveness52 →
FAQ
Tealoveness52 is an npm package that is part of a malicious campaign aimed at generating fraudulent token rewards.
The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.
You should remove the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert to monitor your package-lock.json file for real-time alerts on vulnerabilities without needing to install additional software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
