Malicious Code Injection in unexpected_bird_z3n Package

unexpected_bird_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91521: Malicious code in unexpected_bird_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The unexpected_bird_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package was identified as part of a malicious campaign that aimed to exploit the npm registry by flooding it with derivative packages. The primary functionality of this package is to serve as a token reward mechanism, but it has been compromised to perform harmful actions.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers' reputations and project integrity.

How To Fix

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

npm uninstall unexpected_bird_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 unexpected_bird_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies to identify and remove any malicious packages.

Conclusion

The unexpected_bird_z3n package has been compromised and poses a significant risk to developers using it. It is crucial to remove this package from your projects and monitor your dependencies for any malicious activity. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for unexpected_bird_z3n →

Share this vulnerability

FAQ

The unexpected_bird_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and reputation by introducing malicious code.

You should uninstall the unexpected_bird_z3n package immediately and check for any dependencies that may be affected.

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 any signup.

How To Fix

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

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