Malicious Code Exploit in condemned_grasshopper-gooddev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100822: Malicious code in condemned_grasshopper-gooddev (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 condemned_grasshopper-gooddev package is part of the npm ecosystem, often used in JavaScript projects. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with various packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the condemned_grasshopper-gooddev package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal is to inflate developer reputation scores for token rewards while polluting the npm registry with derivative packages. This can lead to security risks, as it compromises the integrity of the npm ecosystem and can potentially introduce harmful dependencies into projects.

How To Fix

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

npm uninstall condemned_grasshopper-gooddev

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 condemned_grasshopper-gooddev package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The condemned_grasshopper-gooddev package contains malicious code that poses significant risks to the integrity of your projects. It is crucial to remove this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for condemned_grasshopper-gooddev →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for manipulating developer reputation scores.

The malicious code modifies your package.json file, potentially introducing security vulnerabilities and polluting the npm registry.

You should uninstall the condemned_grasshopper-gooddev package immediately and check for any unauthorized changes in your project.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall condemned_grasshopper-gooddev

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