Malicious Code Injection in competent_bird_z3n: A Threat to npm Ecosystem

competent_bird_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100752: Malicious code in competent_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

competent_bird_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is designed to generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that alter its metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the competent_bird_z3n package. This payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The scripts associated with this package (auto.js, autopublish.js, etc.) are designed to automate the creation and publication of these malicious variants, which can lead to significant reputational damage for developers and potential security risks for users who inadvertently install these compromised packages.

How To Fix

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

npm uninstall competent_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 workaround, you can avoid using the competent_bird_z3n package altogether. If it is already in your project, you can remove it by running: npm uninstall competent_bird_z3n. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The competent_bird_z3n package poses a significant threat due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to safeguard against future vulnerabilities.

See every vulnerability recorded for competent_bird_z3n →

Share this vulnerability

FAQ

competent_bird_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of compromised packages.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, leading to potential security risks and reputational damage.

You should uninstall the competent_bird_z3n package immediately and monitor your project for any other potentially compromised packages.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about the latest security advisories in the npm ecosystem.

How To Fix

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

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