Malicious Code Injection in grotesque_kiwi-tool: A Threat to npm Users

grotesque_kiwi-tool Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103402: Malicious code in grotesque_kiwi-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 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 grotesque_kiwi-tool is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to exploit the npm ecosystem by generating and publishing derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious nature of this package poses a significant risk to developers and users who may unknowingly incorporate it into their projects.

Vulnerability Detail

The vulnerability stems from the package's malicious payload, 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 that can pollute the npm registry, making it difficult for developers to identify legitimate packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall grotesque_kiwi-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 grotesque_kiwi-tool package and monitor your project's dependencies for any malicious activity. Consider using tools like Vulert to scan your package-lock.json file for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without requiring any signup.

Conclusion

The grotesque_kiwi-tool package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for grotesque_kiwi-tool →

Share this vulnerability

FAQ

grotesque_kiwi-tool is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry with malicious packages, making it challenging to identify legitimate dependencies and potentially compromising your project's security.

You should uninstall the package immediately using the command npm uninstall grotesque_kiwi-tool and check your project for any other vulnerable dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signup.

No, there are no patches available for grotesque_kiwi-tool as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

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