Malicious Code Injection in Inadequate Grasshopper Dumbs Package

inadequate_grasshopper_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104039: Malicious code in inadequate_grasshopper_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'inadequate_grasshopper_dumbs' package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious packages.

Vulnerability Detail

The vulnerability in the 'inadequate_grasshopper_dumbs' package originates from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially compromising other projects that depend on it. The malicious payload is designed to exploit the npm ecosystem, leading to a loss of trust and security within the community.

How To Fix

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

npm uninstall inadequate_grasshopper_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 measure, you can avoid using the 'inadequate_grasshopper_dumbs' package and any other packages associated with the tea.xyz token reward campaign. Monitor your package dependencies closely and consider using tools like Vulert to check for vulnerabilities in your project. You can access Vulert's playground at https://vulert.com/scanner to assess if your application is affected without needing to sign up.

Conclusion

The 'inadequate_grasshopper_dumbs' package poses a significant risk due to its malicious behavior aimed at manipulating the npm ecosystem. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can help safeguard your projects from potential threats.

See every vulnerability recorded for inadequate_grasshopper_dumbs →

Share this vulnerability

FAQ

It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the package immediately and review your dependencies for any potential risks.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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