Malicious Code Injection in tealove-aruma2: A Threat to npm Users
Summary
MAL-2025-168074: Malicious code in tealove-aruma2 (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-aruma2 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by creating and publishing numerous derivative packages. This package, like others in the campaign, is engineered to inflate developer reputation scores through automated scripts that generate random package names and versions.
Vulnerability Detail
The vulnerability in tealove-aruma2 arises from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to severe ramifications, including the potential for developers to inadvertently install compromised packages, which can lead to further exploitation or data breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-aruma2If 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-aruma2 package and monitor your project's dependencies for any malicious activity. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The tealove-aruma2 package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant and remove any instances of this package from their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for tealove-aruma2 →
FAQ
Tealove-aruma2 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 installation of compromised packages, which may introduce security risks or malicious code into your project.
You should uninstall the package immediately using the command: npm uninstall tealove-aruma2.
Yes, you can use Vulert, which monitors your package-lock.json for 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.
