Malicious Code Vulnerability in desperate_gecko_dumbs Package

desperate_gecko_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101366: Malicious code in desperate_gecko_dumbs (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 desperate_gecko_dumbs 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 are often used to inflate developer reputation scores for token rewards. Its functionality includes creating and publishing packages with randomized names, which can lead to pollution of the npm registry.

Vulnerability Detail

The vulnerability in the desperate_gecko_dumbs package originates from its design to include malicious autopublish scripts. These scripts modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on npm for legitimate packages.

How To Fix

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

npm uninstall desperate_gecko_dumbs

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 desperate_gecko_dumbs package and monitor your package-lock.json file for any unauthorized changes. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your dependencies.

Conclusion

The desperate_gecko_dumbs package contains a significant vulnerability that can lead to the creation of malicious packages in the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any potential threats. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for desperate_gecko_dumbs →

Share this vulnerability

FAQ

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

The vulnerability can lead to the proliferation of malicious packages in the npm registry, potentially compromising your project's integrity.

You should uninstall the desperate_gecko_dumbs package immediately using 'npm uninstall desperate_gecko_dumbs'.

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

There is no patch for the desperate_gecko_dumbs package; the best course of action is to remove it from your project.

How To Fix

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

npm uninstall desperate_gecko_dumbs

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