Malicious Code Injection in Noisy Grouse Z3N Package

noisy_grouse_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95655: Malicious code in noisy_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

Noisy Grouse Z3N is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards through various npm packages. However, this package has been identified as malicious, containing scripts that automatically generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload can affect developers by misrepresenting their contributions and may lead to reputational damage.

How To Fix

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

npm uninstall noisy_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

As a temporary measure, you can avoid using the noisy_grouse_z3n package and look for alternative packages that provide similar functionality without the risk of malicious code. Always verify the integrity of packages before installation.

Conclusion

The noisy_grouse_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and adopt best practices for dependency management to safeguard their projects.

See every vulnerability recorded for noisy_grouse_z3n →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json and republishes variants to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json. Visit Vulert Scanner to check your application without any signup.

You should uninstall the package immediately using 'npm uninstall noisy_grouse_z3n' and review your dependencies for any other potentially malicious packages.

Yes, consider looking for reputable packages that offer similar functionality without the associated risks. Always check the package's reputation and reviews.

Regularly update your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor for vulnerabilities in your projects.

How To Fix

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

npm uninstall noisy_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