Malicious Code Injection in tealove-aruma: A Threat to npm Users

tealove-aruma Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168062: Malicious code in tealove-aruma (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

tealove-aruma is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of tokens through various npm packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm registry and the applications that depend on it. The package's functionality is undermined by its ability to generate and publish derivative packages with altered metadata, which can lead to reputation inflation and potential security risks for developers.

Vulnerability Detail

The vulnerability in tealove-aruma originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry by continuously republishing variants of the package, thereby inflating developer reputation scores for token rewards. The ramifications of this vulnerability include the potential for developers to unknowingly install compromised packages, 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-aruma

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 remove the tealove-aruma package from your project by executing the command: 'npm uninstall tealove-aruma'. This will prevent any potential malicious activity associated with the package until a fix is applied.

Conclusion

The tealove-aruma package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers are urged to take immediate action by updating or uninstalling the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for tealove-aruma →

Share this vulnerability

FAQ

tealove-aruma is an npm package associated with the tea.xyz token reward campaign, designed to distribute tokens through various npm packages.

The package modifies package.json files to remove private flags, changes version numbers, and generates random package names, leading to pollution of the npm registry.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can identify if your application is affected by vulnerabilities like that in tealove-aruma.

To prevent the installation of malicious packages, regularly update your dependencies, audit your packages using tools like npm audit, and utilize services like Vulert for real-time monitoring.

If you have installed tealove-aruma, it is recommended to uninstall the package immediately and check for any other dependencies that may have been affected.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-aruma

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback