Malicious Code Injection in tasty_chicken_z3n Package

tasty_chicken_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109512: Malicious code in tasty_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 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 tasty_chicken_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the tasty_chicken_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. This allows the package to generate random names and continuously republish itself, polluting the npm registry. The malicious payload can lead to security risks, including the potential for unauthorized access to sensitive data and the degradation of the integrity of the npm ecosystem.

How To Fix

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

npm uninstall tasty_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 tasty_chicken_z3n package and replace it with a trusted alternative that provides similar functionality. Always verify the source and reputation of any package before including it in your project.

Conclusion

The tasty_chicken_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications.

See every vulnerability recorded for tasty_chicken_z3n →

Share this vulnerability

FAQ

The tasty_chicken_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to unauthorized access to sensitive data and can compromise the integrity of your application by introducing malicious code.

You should uninstall the tasty_chicken_z3n package immediately and replace it with a trusted alternative.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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