Malicious Code Injection in disabled_blackbird_z3n Package

disabled_blackbird_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101603: Malicious code in disabled_blackbird_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 disabled_blackbird_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the disabled_blackbird_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal of this malicious payload is to inflate developer reputation scores for the tea protocol token rewards by continuously republishing variants, thereby polluting the npm registry. This can lead to significant security risks, including the potential for unauthorized access to sensitive data and the spread of further malicious packages.

How To Fix

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

npm uninstall disabled_blackbird_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 prevent the installation of the disabled_blackbird_z3n package by adding it to your project's .npmrc file with the following line: package-lock=false. This will help avoid any accidental installations until the vulnerability is fully addressed.

Conclusion

The disabled_blackbird_z3n package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to take immediate action to remove this package and monitor their projects for any potential vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for disabled_blackbird_z3n →

Share this vulnerability

FAQ

The disabled_blackbird_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, potentially exposing your project to security risks and polluting the npm registry with unauthorized packages.

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

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using your package-lock.json file. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly audit your dependencies using tools like npm audit, and consider using services like Vulert to monitor your projects for vulnerabilities.

How To Fix

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

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