Malicious Code Injection in wee_ocelot_z3n: A Threat to npm Ecosystem

wee_ocelot_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92182: Malicious code in wee_ocelot_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

wee_ocelot_z3n is an npm package that has been implicated in a malicious campaign targeting the npm ecosystem. It is part of a broader initiative that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores in exchange for token rewards, specifically for the tea.xyz protocol. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in wee_ocelot_z3n originates from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these compromised packages. 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 wee_ocelot_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 remove the wee_ocelot_z3n package from your project by executing the following command: npm uninstall wee_ocelot_z3n. This will prevent any malicious code from executing until a patch is available.

Conclusion

The wee_ocelot_z3n package has been identified as a malicious entity within the npm ecosystem, capable of compromising the integrity of the registry and posing risks to developers. It is crucial to take immediate action by updating or uninstalling the package to safeguard your applications.

See every vulnerability recorded for wee_ocelot_z3n →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json files and repackages the npm registry with harmful derivatives.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Using this package can lead to security breaches, reputation damage, and the risk of your application being compromised through malicious code.

Regularly updating your dependencies, using tools like Vulert for monitoring, and auditing your packages can help prevent vulnerabilities.

Uninstall the package immediately using 'npm uninstall wee_ocelot_z3n' and check for any updates or patches.

How To Fix

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

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