Malicious Code Injection in apparent_hummingbird_z3n Package

apparent_hummingbird_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93250: Malicious code in apparent_hummingbird_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 apparent_hummingbird_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like others in the campaign, is designed to manipulate npm's publishing system by creating and publishing derivative packages with randomized names. It aims to inflate developer reputation scores for token rewards, making it a target for malicious exploitation.

Vulnerability Detail

The vulnerability in the apparent_hummingbird_z3n package originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to a polluted npm registry. The malicious payload can compromise the integrity of the npm ecosystem, potentially affecting developers who rely on these packages for legitimate purposes.

How To Fix

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

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

Conclusion

The apparent_hummingbird_z3n package contains a serious vulnerability that allows for the injection of malicious code, which can compromise the integrity of the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your project.

See every vulnerability recorded for apparent_hummingbird_z3n →

Share this vulnerability

FAQ

The apparent_hummingbird_z3n package is an npm package associated with a token reward campaign that manipulates the npm registry.

The vulnerability can lead to the injection of malicious code, compromising the integrity of your project and potentially affecting other dependencies.

Check the npm registry for any updates to the apparent_hummingbird_z3n package that may address the vulnerability.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

If you cannot update the package, consider removing it from your project and looking for a secure alternative.

How To Fix

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

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