Malicious Code Injection in flying_ox_z3n Package

flying_ox_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94554: Malicious code in flying_ox_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

The flying_ox_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm registry but has been compromised to include malicious code. The vulnerability stems from its ability to manipulate package metadata, which can lead to severe repercussions for developers and users relying on this package.

Vulnerability Detail

The vulnerability in the flying_ox_z3n package involves the injection of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the automatic publication of derivative packages. The origin of this vulnerability is linked to a campaign aimed at inflating developer reputation scores for token rewards, which can pollute the npm registry and compromise the integrity of the ecosystem.

How To Fix

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

npm uninstall flying_ox_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, consider removing the flying_ox_z3n package from your project until a secure version is available. You can do this using the command: npm uninstall flying_ox_z3n. Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The flying_ox_z3n package has been identified as containing malicious code that poses a significant risk to developers and users. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for flying_ox_z3n →

Share this vulnerability

FAQ

The flying_ox_z3n package is an npm package that was part of a token reward campaign but has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to unauthorized package publications and compromising your project's integrity.

You can use Vulert to monitor your application for vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed the flying_ox_z3n package, it is recommended to uninstall it immediately and monitor your project for any unusual activity.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and keep your packages updated to minimize the risk of vulnerabilities.

How To Fix

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

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