Malicious Code Injection in wasteful_grasshopper_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97317: Malicious code in wasteful_grasshopper_requirement (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 wasteful_grasshopper_requirement package is part of the npm ecosystem, often utilized in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages designed to inflate developer reputation scores. This package, like others in the campaign, is likely to contain harmful scripts that can compromise the integrity of projects that depend on it.

Vulnerability Detail

The vulnerability in the wasteful_grasshopper_requirement package stems from its inclusion in a malicious campaign that modifies package.json files to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem.

How To Fix

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

npm uninstall wasteful_grasshopper_requirement

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 prevent the installation of the wasteful_grasshopper_requirement package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include this package in its dependencies or devDependencies.

Conclusion

The wasteful_grasshopper_requirement package poses a significant security risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in real-time. Staying informed and proactive is key to maintaining the security of your software.

See every vulnerability recorded for wasteful_grasshopper_requirement →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. Visit Vulert Scanner to check if your application is affected.

Using this package can lead to unauthorized access to sensitive data, compromise the integrity of your project, and contribute to the pollution of the npm registry.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to your packages.

Immediately uninstall the package using 'npm uninstall wasteful_grasshopper_requirement' and check your project for any other potentially malicious dependencies.

How To Fix

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

npm uninstall wasteful_grasshopper_requirement

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