Malicious Code Injection in Noisy Chicken Z3N Package: A Threat to NPM Users

noisy_chicken_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98837: Malicious code in noisy_chicken_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 'noisy_chicken_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 such packages is to manipulate developer reputation scores through automated publishing scripts, which can lead to a polluted npm registry and potential security risks for users.

Vulnerability Detail

The vulnerability in the 'noisy_chicken_z3n' package originates from its design to include malicious scripts that modify the package.json file. This includes removing private flags, altering version numbers, and generating random package names, which can lead to the proliferation of derivative packages. The malicious payload can compromise the integrity of the npm registry and potentially expose users to further security risks, as these packages can be used to distribute harmful code.

How To Fix

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

npm uninstall noisy_chicken_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 workaround, you can avoid using the 'noisy_chicken_z3n' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the source and reputation of packages before including them in your project.

Conclusion

The 'noisy_chicken_z3n' package poses a significant threat to npm users due to its malicious code designed to manipulate package publishing. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security. Utilizing tools like Vulert can help in identifying and alerting you to such risks in real-time.

See every vulnerability recorded for noisy_chicken_z3n →

Share this vulnerability

FAQ

It is an npm package that has been identified as malicious, designed to manipulate developer reputation scores through automated publishing.

The vulnerability can lead to the proliferation of malicious packages, compromising the integrity of your project and potentially exposing it to security risks.

You should uninstall the 'noisy_chicken_z3n' package immediately using 'npm uninstall noisy_chicken_z3n' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, look for reputable packages that offer similar functionality but have a verified history and community support.

How To Fix

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

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