Malicious Code Injection in growing_bass_z3n Package - npm Vulnerability

growing_bass_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94762: Malicious code in growing_bass_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The growing_bass_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the growing_bass_z3n package, which contains scripts designed to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. This can lead to a loss of developer reputation and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall growing_bass_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, avoid using the growing_bass_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to identify any potential vulnerabilities.

Conclusion

The growing_bass_z3n package poses a significant risk due to its malicious code that manipulates package metadata. It is essential for developers to be vigilant about the packages they use and to take proactive steps to secure their applications. Utilizing tools like Vulert can aid in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for growing_bass_z3n →

Share this vulnerability

FAQ

The growing_bass_z3n package is an npm package that has been compromised to include malicious scripts aimed at manipulating package metadata for fraudulent purposes.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

The risks include loss of developer reputation, potential security breaches, and the pollution of the npm registry with malicious packages, which can affect other developers and applications.

To prevent such vulnerabilities, regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools like Vulert to monitor for vulnerabilities.

If you have used the growing_bass_z3n package, it is crucial to uninstall it immediately and replace it with a secure alternative. Regularly check for updates and patches for your dependencies.

How To Fix

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

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