Malicious Code Vulnerability in terrible_gopher-appteadev: Exploiting npm for Token Rewards

terrible_gopher-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109554: Malicious code in terrible_gopher-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 package terrible_gopher-appteadev 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 are intended to inflate developer reputation scores for token rewards. The package's functionality includes creating random package names and modifying existing package metadata.

Vulnerability Detail

This vulnerability originates from the package's malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly integrate this package into their projects, leading to compromised package integrity and reputation.

How To Fix

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

npm uninstall terrible_gopher-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 package from your project by executing the command: npm uninstall terrible_gopher-appteadev. This will prevent any malicious code from executing in your environment.

Conclusion

The terrible_gopher-appteadev package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities.

See every vulnerability recorded for terrible_gopher-appteadev →

Share this vulnerability

FAQ

terrible_gopher-appteadev is an npm package associated with the tea.xyz token reward campaign, designed to automatically generate and publish derivative packages.

The vulnerability can compromise your project's package integrity by modifying package metadata and introducing malicious code, which may lead to security risks.

If you have installed this package, it is crucial to uninstall it immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check if your application is affected using the Vulert playground without any signup.

To prevent similar vulnerabilities, regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert for real-time monitoring.

How To Fix

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

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