Malicious Code Vulnerability in changing_gerbil-appteadev Package

changing_gerbil-appteadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100322: Malicious code in changing_gerbil-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 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 changing_gerbil-appteadev package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability originates from the malicious payload embedded within the changing_gerbil-appteadev package. It modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially affect other packages and applications relying on npm. The malicious scripts (auto.js, autopublish.js, etc.) are designed to automate these processes, making it difficult for developers to detect and mitigate the issue.

How To Fix

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

npm uninstall changing_gerbil-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 avoid using the changing_gerbil-appteadev package altogether. If your project requires similar functionality, consider looking for alternative packages that do not have known vulnerabilities. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Conclusion

The changing_gerbil-appteadev package contains a serious vulnerability due to malicious code that alters package configurations and repopulates the npm registry with compromised variants. It is crucial for developers to uninstall this package and monitor their dependencies for vulnerabilities using tools like Vulert to maintain application security.

See every vulnerability recorded for changing_gerbil-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 derivative packages.

The malicious code can compromise your application's integrity by modifying package configurations and republishing variants, potentially leading to security risks.

You should uninstall the package immediately and check for any updates or patches from the maintainers.

Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

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

How To Fix

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

npm uninstall changing_gerbil-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