Malicious Code Injection in grape-notthedevs Package

grape-notthedevs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103348: Malicious code in grape-notthedevs (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The grape-notthedevs package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate the development and management of Node.js applications. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, impacting developers and users alike.

Vulnerability Detail

The vulnerability originates from the grape-notthedevs package, which is associated with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants to pollute the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall grape-notthedevs

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 remove the grape-notthedevs package from your project by executing: npm uninstall grape-notthedevs. This will prevent the execution of any malicious scripts associated with the package until a secure version is released.

Conclusion

The grape-notthedevs package has been identified as a source of malicious code that can compromise the integrity of JavaScript applications. It is essential for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for grape-notthedevs →

Share this vulnerability

FAQ

The grape-notthedevs package is a JavaScript package in the npm ecosystem, used for various development purposes but has been compromised with malicious code.

The malicious code modifies your project's package.json, potentially exposing it to security vulnerabilities and affecting the integrity of your application.

If you have installed the grape-notthedevs package, it is crucial to uninstall it immediately and check for any updates or patches.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Regularly updating your packages, using tools like Vulert for monitoring, and auditing your dependencies can help prevent vulnerabilities from affecting your projects.

How To Fix

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

npm uninstall grape-notthedevs

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