Malicious Code Injection in tealove-aruma16: A Threat to npm Packages
Summary
MAL-2025-168070: Malicious code in tealove-aruma16 (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-aruma16 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 manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of tealove-aruma16 is compromised due to its malicious intent, posing a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-aruma16 originates from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can affect developers relying on legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-aruma16
If 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 the tealove-aruma16 package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unexpected changes and remove any suspicious packages immediately.
Conclusion
The tealove-aruma16 package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant, remove such packages, and utilize tools like Vulert to monitor for vulnerabilities in their projects. Staying informed and proactive can help maintain the integrity of your applications.
See every vulnerability recorded for tealove-aruma16 →
FAQ
tealove-aruma16 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the pollution of the npm registry, potentially introducing malicious code into your project and compromising its security.
You should uninstall the package immediately using 'npm uninstall tealove-aruma16' and check for any dependencies that may be affected.
You can use tools like Vulert, which monitors your package-lock.json file 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 any signup.