Malicious Code Injection in stale_kiwi_z3n Package: A Threat to npm Ecosystem

stale_kiwi_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96745: Malicious code in stale_kiwi_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 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 stale_kiwi_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.

Vulnerability Detail

The vulnerability in stale_kiwi_z3n is rooted in its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising other packages. The origin of this issue is linked to the broader trend of malicious packages targeting npm to exploit developer incentives.

How To Fix

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

npm uninstall stale_kiwi_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 prevent the installation of stale_kiwi_z3n by using npm's package-lock.json file to lock your dependencies. However, the best course of action is to remove the package entirely.

Conclusion

The stale_kiwi_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove such packages from their projects to maintain security and integrity. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for stale_kiwi_z3n →

Share this vulnerability

FAQ

stale_kiwi_z3n is an npm package that is part of a malicious campaign to inflate developer reputation scores by generating and publishing derivative packages.

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

You should uninstall the stale_kiwi_z3n package immediately and ensure your project dependencies are updated.

There is no patch for the stale_kiwi_z3n package as it is inherently malicious. The best action is to remove it from your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

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