Malicious Code Injection in growing_jay-tool: A Threat to npm Packages

growing_jay-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103409: Malicious code in growing_jay-tool (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 growing_jay-tool package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign linked to the tea.xyz token reward initiative. This campaign has led to the proliferation of packages that manipulate the npm registry, posing significant risks to developers and their projects.

Vulnerability Detail

The vulnerability in growing_jay-tool stems from its association with a malicious campaign that employs scripts to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and creating numerous variants to inflate developer reputation scores. This behavior not only pollutes the npm registry but also compromises the integrity of the packages, making it difficult for developers to trust the ecosystem.

How To Fix

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

npm uninstall growing_jay-tool

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 growing_jay-tool package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package dependencies for vulnerabilities.

Conclusion

The growing_jay-tool package poses a significant risk due to its malicious code injection capabilities. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for growing_jay-tool →

Share this vulnerability

FAQ

growing_jay-tool is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the injection of malicious code into your project, potentially compromising its security and integrity.

You should uninstall the growing_jay-tool package immediately and check for any dependencies that may be affected.

Yes, you can use Vulert to monitor your package-lock.json for vulnerabilities in real-time without needing to access the code or install anything.

Absolutely! You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall growing_jay-tool

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