Malicious Code Injection in rapid_grouse_z3n Package

rapid_grouse_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96182: Malicious code in rapid_grouse_z3n (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 rapid_grouse_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.

Vulnerability Detail

The vulnerability in the rapid_grouse_z3n package stems from its association with a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious code modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall rapid_grouse_z3n

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The rapid_grouse_z3n package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for rapid_grouse_z3n →

Share this vulnerability

FAQ

The rapid_grouse_z3n package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The malicious code modifies your package.json file, potentially leading to the use of compromised packages and exposing your application to security risks.

You should uninstall the rapid_grouse_z3n package immediately and check for any dependencies that may rely on it.

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

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall rapid_grouse_z3n

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