Malicious Code Injection in tealove-aruma47 Package: npm Vulnerability Summary

tealove-aruma47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168104: Malicious code in tealove-aruma47 (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-aruma47 package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with 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 the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability in the tealove-aruma47 package originates from its design to include autopublish scripts that automatically modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and the undermining 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-aruma47

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-aruma47 package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The tealove-aruma47 package poses significant risks due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.

See every vulnerability recorded for tealove-aruma47 →

Share this vulnerability

FAQ

Tealove-aruma47 is an npm package that is part of a token reward campaign, designed to manipulate the npm registry through the creation of derivative packages.

The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project inadvertently uses compromised packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the tealove-aruma47 package, it is advisable to remove it immediately and check for any alternative packages that do not pose security risks.

Yes, there are many npm packages that provide similar functionalities without the associated risks. Always review the package's reputation and security history before installation.

How To Fix

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

npm uninstall tealove-aruma47

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