Malicious Code Injection in outdoor_urial_z3n Package

outdoor_urial_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106824: Malicious code in outdoor_urial_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The outdoor_urial_z3n package is part of the npm ecosystem, commonly used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. This package, like others in the campaign, has been designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the outdoor_urial_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this vulnerability is tied to the tea.xyz token reward campaign, which aims to inflate developer reputation scores by polluting the npm registry with derivative packages. The ramifications include potential security risks for applications relying on this package, as well as contributing to the degradation of the npm ecosystem.

How To Fix

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

npm uninstall outdoor_urial_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 outdoor_urial_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in your package-lock.json file.

Conclusion

The outdoor_urial_z3n package contains malicious code that poses a significant risk to applications using it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your project.

See every vulnerability recorded for outdoor_urial_z3n →

Share this vulnerability

FAQ

The outdoor_urial_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the pollution of the npm registry.

You should uninstall the outdoor_urial_z3n package immediately using the command: npm uninstall outdoor_urial_z3n.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

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