Malicious Code Injection in Cuddly Warbler Z3N Package

cuddly_warbler_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93880: Malicious code in cuddly_warbler_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 Warbler Z3N is an npm package that has been associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. However, it has been compromised to include malicious code that alters its own package configuration.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious scripts within the cuddly_warbler_z3n package. These scripts are designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, particularly those associated with token reward schemes.

How To Fix

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

npm uninstall cuddly_warbler_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 remove the cuddly_warbler_z3n package from your project by executing: npm uninstall cuddly_warbler_z3n. This will prevent any malicious scripts from executing while you seek a secure alternative.

Conclusion

The cuddly_warbler_z3n package has been identified as containing malicious code that compromises the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects from potential threats.

See every vulnerability recorded for cuddly_warbler_z3n →

Share this vulnerability

FAQ

Cuddly_warbler_z3n is an npm package that was part of a token reward campaign, designed to automatically generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of other packages in your project.

You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.

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

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

How To Fix

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

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