Malicious Code Injection in eager_owl_z3n Package - npm Vulnerability

eager_owl_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94156: Malicious code in eager_owl_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eager_owl_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in the eager_owl_z3n package originates from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by misrepresenting their packages and inflating reputation scores fraudulently.

How To Fix

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

npm uninstall eager_owl_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 eager_owl_z3n package altogether. If it is already included in your project, remove it by running: npm uninstall eager_owl_z3n. Additionally, consider using Vulert to monitor your project for vulnerabilities. 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 eager_owl_z3n package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to ensure the security of their applications.

See every vulnerability recorded for eager_owl_z3n →

Share this vulnerability

FAQ

The eager_owl_z3n package is part of the npm ecosystem and is involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may misrepresent your project's integrity, potentially harming your reputation as a developer.

If you have installed the eager_owl_z3n package, it is advisable to uninstall it immediately using the command: npm uninstall eager_owl_z3n.

Currently, there is no specific patch version available for the eager_owl_z3n package. It is best to remove the package until a safe version is released.

You can use Vulert to monitor your project for open-source vulnerabilities in real-time. Visit https://vulert.com to learn more and check your application.

How To Fix

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

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