Malicious Code Detected in tealove-aruma34: A Threat to npm Users

tealove-aruma34 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168090: Malicious code in tealove-aruma34 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package tealove-aruma34 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm ecosystem by flooding it with derivative packages that have randomized names. This behavior is intended to inflate developer reputation scores for rewards related to the tea protocol. The package's functionality is compromised due to its malicious intent, making it a significant risk for users relying on npm for package management.

Vulnerability Detail

The vulnerability in tealove-aruma34 originates from its design to include autopublish scripts that automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. This results in pollution of the npm registry and can lead to security risks for developers who may unknowingly install these malicious packages. The continuous republishing of variants exacerbates the issue, making it difficult to track and mitigate the threat.

How To Fix

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

npm uninstall tealove-aruma34

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 measure, avoid using the tealove-aruma34 package and consider using alternative packages that provide similar functionality without the associated risks. You can also use the following command to uninstall the package: npm uninstall tealove-aruma34.

Conclusion

The tealove-aruma34 package poses a significant threat to npm users due to its malicious code and behavior. It is crucial for developers to be vigilant about their dependencies and take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring for vulnerabilities and ensuring the security of your projects.

See every vulnerability recorded for tealove-aruma34 →

Share this vulnerability

FAQ

Tealove-aruma34 is an npm package that is part of a malicious campaign aimed at manipulating the npm registry for token rewards.

The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and security.

You should uninstall the package immediately and check your project for any other potentially malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.

Yes, consider using other reputable packages that offer similar functionality without the risks associated with tealove-aruma34.

How To Fix

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

npm uninstall tealove-aruma34

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