Malicious Code Injection in shared_ocelot_z3n Package

shared_ocelot_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108605: Malicious code in shared_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The shared_ocelot_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that manipulate its own metadata and proliferate harmful variants across the npm registry.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the shared_ocelot_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which can lead to pollution of the npm registry and potential exploitation by attackers. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, particularly those associated with token reward schemes.

How To Fix

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

npm uninstall shared_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 avoid using the shared_ocelot_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The shared_ocelot_z3n package has been identified as containing malicious code that can compromise your project's integrity. It is essential to uninstall this package and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for shared_ocelot_z3n →

Share this vulnerability

FAQ

The shared_ocelot_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the proliferation of harmful package variants, potentially compromising your project's integrity.

If you have installed the shared_ocelot_z3n package, you should uninstall it immediately using the command npm uninstall shared_ocelot_z3n.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file. You can check if your application is affected by visiting the Vulert playground.

To prevent similar vulnerabilities, always review package dependencies, check for community feedback, and use tools like Vulert to monitor for vulnerabilities in your project.

How To Fix

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

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