Malicious Code Injection in tall_mockingbird_z3n: A Threat to npm Packages

tall_mockingbird_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109446: Malicious code in tall_mockingbird_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 package 'tall_mockingbird_z3n' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to its malicious intent, posing a significant risk to developers and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'tall_mockingbird_z3n' originates from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially damaging the reputation of legitimate developers. The malicious payload can also facilitate further exploitation by allowing unauthorized access to sensitive information or enabling the distribution of harmful code.

How To Fix

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

npm uninstall tall_mockingbird_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 'tall_mockingbird_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'tall_mockingbird_z3n' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for tall_mockingbird_z3n →

Share this vulnerability

FAQ

The 'tall_mockingbird_z3n' package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially damaging your project's reputation and exposing it to further security risks.

You should uninstall the 'tall_mockingbird_z3n' package immediately and monitor your project for any other vulnerabilities.

Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.

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

How To Fix

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

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