Critical Malicious Code Vulnerability in grew-plugins Package

grew-plugins Updated 02 Oct 2025

Summary

16/05/2025
CRITICAL
No i
Critical
Not published

MAL-2025-3891: Malicious code in grew-plugins (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 grew-plugins package is a collection of plugins designed to enhance the functionality of the grew framework, which is used for natural language processing tasks. This package allows developers to extend the capabilities of their applications by integrating various plugins. However, the package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the grew-plugins package, as reported by the GitHub Security Advisory (GHSA). Any system with this package installed is considered fully compromised, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been handed over to an external entity.

How To Fix

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

npm uninstall grew-plugins

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 workaround, if you need to maintain functionality while addressing the vulnerability, consider using alternative plugins that do not have known security issues. Always ensure to review the security status of any packages before installation.

Conclusion

The grew-plugins package has been identified as containing malicious code, posing serious security risks to any system that utilizes it. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for grew-plugins →

Share this vulnerability

FAQ

Immediately uninstall the grew-plugins package and rotate any secrets or keys stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and keep your packages updated to their latest secure versions.

The vulnerability details were sourced from the GitHub Security Advisory (GHSA) and are documented in the Open Source Vulnerability format.

How To Fix

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

npm uninstall grew-plugins

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