Malicious Code Injection in geographical_dingo-apptea: npm Package Vulnerability

geographical_dingo-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103108: Malicious code in geographical_dingo-apptea (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 geographical_dingo-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package is designed to automatically generate and publish derivative packages, potentially compromising the integrity of the npm ecosystem. Its functionality is primarily linked to token rewards, but its malicious behavior poses significant risks to developers and users alike.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the geographical_dingo-apptea package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and inflating developer reputation scores fraudulently. This can lead to security risks for applications relying on these packages, as they may inadvertently incorporate compromised code.

How To Fix

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

npm uninstall geographical_dingo-apptea

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 geographical_dingo-apptea package altogether. If it is already included in your project, remove it by running: npm uninstall geographical_dingo-apptea. Additionally, consider using Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The geographical_dingo-apptea package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.

See every vulnerability recorded for geographical_dingo-apptea →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, potentially compromising your project's integrity.

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

You should uninstall the geographical_dingo-apptea package immediately using the command: npm uninstall geographical_dingo-apptea.

Currently, there is no patched version available. It is recommended to remove the package until a secure version is released.

How To Fix

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

npm uninstall geographical_dingo-apptea

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