Malicious Code Injection in grand_ox_z3n: A Threat to npm Packages

grand_ox_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103344: Malicious code in grand_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 package grand_ox_z3n is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with packages that contain malicious scripts. These scripts are designed to manipulate package metadata and inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in grand_ox_z3n originates from its association with malicious scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and create random package names, leading to the pollution of the npm registry. The ramifications include potential security risks for developers and users who may inadvertently install these compromised packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall grand_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, you can avoid using the grand_ox_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The grand_ox_z3n package poses a significant risk due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for any vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for grand_ox_z3n →

Share this vulnerability

FAQ

grand_ox_z3n is an npm package that has been linked to a malicious campaign aimed at manipulating package metadata for token rewards.

The malicious code can alter your package.json file, leading to the installation of compromised packages and potential security vulnerabilities in your project.

You should remove the grand_ox_z3n package from your project immediately and monitor your dependencies for any other malicious packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application against vulnerabilities using the Vulert playground without any signup.

Yes, you should look for alternative npm packages that provide similar functionality but have a good reputation and are actively maintained.

How To Fix

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

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