Malicious Code Injection in additional_grasshopper-toolteadev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99124: Malicious code in additional_grasshopper-toolteadev (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 additional_grasshopper-toolteadev package is part of the npm ecosystem, typically used for development purposes. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages designed to manipulate npm's registry. This package, like others in the campaign, has been found to contain scripts that automatically generate and publish derivative packages, potentially compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the additional_grasshopper-toolteadev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall additional_grasshopper-toolteadev

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 additional_grasshopper-toolteadev package until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The additional_grasshopper-toolteadev package has been identified as containing malicious code that can compromise the integrity of your npm projects. It is crucial to update to a secure version and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for additional_grasshopper-toolteadev →

Share this vulnerability

FAQ

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

The malicious code can modify your package.json file, remove private flags, and republish altered versions of your package, leading to potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

As a workaround, avoid using the additional_grasshopper-toolteadev package until a secure version is available, and regularly audit your dependencies.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall additional_grasshopper-toolteadev

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