Malicious Code Injection in outstanding_moose_z3n: A Threat to npm Packages

outstanding_moose_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98859: Malicious code in outstanding_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 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 outstanding_moose_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for the tea protocol token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability in outstanding_moose_z3n originates from its involvement in the tea.xyz token reward campaign. This package contains scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, which can lead to confusion, misuse, and potential security risks for developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall outstanding_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, you can avoid using the outstanding_moose_z3n package and monitor your project for any dependencies that may inadvertently include it. Regularly check your package-lock.json file for any suspicious entries.

Conclusion

The outstanding_moose_z3n package poses a significant security risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package from their projects and remain vigilant about the packages they use. Utilizing tools like Vulert can help in monitoring and alerting for open-source vulnerabilities effectively.

See every vulnerability recorded for outstanding_moose_z3n →

Share this vulnerability

FAQ

outstanding_moose_z3n is an npm package identified as part of a malicious campaign that exploits the npm registry.

The vulnerability can lead to the introduction of malicious code, which may compromise your project's security and integrity.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you have installed outstanding_moose_z3n, you should uninstall it immediately using 'npm uninstall outstanding_moose_z3n' and review your dependencies.

Regularly update your dependencies, use trusted packages, and monitor your project with tools like Vulert to stay informed about vulnerabilities.

How To Fix

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

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