Malicious Code Injection in Costly Kiwi Requirement Package

costly_kiwi_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93831: Malicious code in costly_kiwi_requirement (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 'costly_kiwi_requirement' package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for applications that depend on them.

Vulnerability Detail

The vulnerability originates from the malicious scripts embedded within the 'costly_kiwi_requirement' package. These scripts modify the package.json file to remove private flags, alter version numbers, and generate random package names, thereby polluting the npm registry. The ramifications include potential exposure of sensitive information, unauthorized access to systems, and the risk of dependency confusion attacks, where malicious packages are inadvertently used in place of legitimate ones.

How To Fix

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

npm uninstall costly_kiwi_requirement

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 workaround, you can remove the 'costly_kiwi_requirement' package from your project by executing the command: 'npm uninstall costly_kiwi_requirement'. This will prevent the execution of any malicious scripts associated with the package until a fix is applied.

Conclusion

The 'costly_kiwi_requirement' package poses a significant security risk due to its malicious code designed to manipulate package management processes. It is crucial to take immediate action by updating or removing the package to safeguard your application from potential threats.

See every vulnerability recorded for costly_kiwi_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive information and allowing for dependency confusion attacks.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall costly_kiwi_requirement

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