Malicious Code Injection in tealove-aruma14 Package

tealove-aruma14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168068: Malicious code in tealove-aruma14 (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 tealove-aruma14 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages typically contain scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The presence of such malicious code poses significant risks to developers and users relying on this package.

Vulnerability Detail

The vulnerability in the tealove-aruma14 package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for users who unknowingly install these malicious packages, as they may introduce harmful code into their applications.

How To Fix

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

npm uninstall tealove-aruma14

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 workaround, consider using a package-lock.json file to monitor and control the versions of your dependencies. This can help prevent the installation of malicious packages. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities in real-time without requiring access to the code or installation.

Conclusion

The tealove-aruma14 package has been identified as containing malicious code that poses significant risks to users and developers. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for tealove-aruma14 →

Share this vulnerability

FAQ

Tealove-aruma14 is a package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json, removes private flags, and can lead to the installation of harmful packages that may compromise your application's security.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using the command: npm uninstall tealove-aruma14.

Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.

How To Fix

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

npm uninstall tealove-aruma14

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