Malicious Code Injection in tealove-aruma27: A Threat to npm Packages
Summary
MAL-2025-168082: Malicious code in tealove-aruma27 (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 tealove-aruma27 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages automatically, which can inflate developer reputation scores for token rewards. This package, like others in the campaign, includes scripts that modify package metadata and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in tealove-aruma27 stems from its malicious payload that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-aruma27If 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 tealove-aruma27 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The tealove-aruma27 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for tealove-aruma27 →
FAQ
Tealove-aruma27 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation and publication of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, compromising its security and potentially leading to data breaches or loss of trust in your software.
You should uninstall the package immediately using the command npm uninstall tealove-aruma27 and check for any dependencies that may be affected.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.
Yes, you should look for reputable packages that provide similar functionality without the associated risks. Always verify the package's integrity and community trust before installation.
