Malicious Code Injection in preferred_rhinoceros-appteadev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107197: Malicious code in preferred_rhinoceros-appteadev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The preferred_rhinoceros-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with numerous variants.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, potentially harming developers' reputations and the integrity of the ecosystem.

How To Fix

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

npm uninstall preferred_rhinoceros-appteadev

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 preferred_rhinoceros-appteadev package from your project by executing: npm uninstall preferred_rhinoceros-appteadev. This will prevent any malicious code from executing until a fix is applied.

Conclusion

The preferred_rhinoceros-appteadev package contains a significant vulnerability that can compromise the integrity of your project and the npm registry. It is crucial to take immediate action by updating or removing the package to safeguard your application.

See every vulnerability recorded for preferred_rhinoceros-appteadev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation and publication of packages.

The vulnerability can lead to the modification of your package.json file and the pollution of the npm registry, which may harm your project's reputation.

You should immediately update the package to a patched version or uninstall it to mitigate the risk of exploitation.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software without needing access to the code or installation.

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

How To Fix

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

npm uninstall preferred_rhinoceros-appteadev

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