Malicious Code Injection in Vitreous Moose Z3N Package

vitreous_moose_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97277: Malicious code in vitreous_moose_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

Vitreous Moose Z3N is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate its own metadata and continuously republish variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in the Vitreous Moose Z3N package stems from its inclusion in a broader scheme that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly incorporate these malicious packages into their projects. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to potential security breaches and reputation damage for developers.

How To Fix

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

npm uninstall vitreous_moose_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, avoid using the Vitreous Moose Z3N package in your projects. If it is already included, consider replacing it with a reputable alternative package that provides similar functionality without the associated risks.

Conclusion

The Vitreous Moose Z3N package poses a significant risk due to its malicious code that alters project metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for vitreous_moose_z3n →

Share this vulnerability

FAQ

Vitreous Moose Z3N is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

Incorporating the Vitreous Moose Z3N package can lead to security breaches, as it modifies your project's metadata and can introduce other malicious packages into your environment.

You should uninstall the Vitreous Moose Z3N package immediately using the command npm uninstall vitreous_moose_z3n and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies using tools like npm audit and stay updated on the latest security advisories for the packages you use.

How To Fix

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

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