Malicious Code Injection in Cuddly Pigeon Z3N Package

cuddly_pigeon_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101138: Malicious code in cuddly_pigeon_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

Cuddly Pigeon Z3N is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. Its primary function is to facilitate the generation and publication of derivative packages. However, it has been exploited to include malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code in the cuddly_pigeon_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores and pollute the npm registry with numerous derivative packages. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as a degradation of the npm ecosystem's reliability.

How To Fix

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

npm uninstall cuddly_pigeon_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 cuddly_pigeon_z3n package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The cuddly_pigeon_z3n package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for cuddly_pigeon_z3n →

Share this vulnerability

FAQ

Cuddly Pigeon Z3N is an npm package involved in a token reward campaign, which has been compromised to include malicious scripts.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized derivative packages, potentially compromising your project's integrity.

You should uninstall the cuddly_pigeon_z3n package immediately using 'npm uninstall cuddly_pigeon_z3n' and check for any unauthorized changes in your project.

Yes, you should look for other npm packages that provide similar functionality without the associated risks of malicious code.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your 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 cuddly_pigeon_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