Malicious Code Injection in outside_ocelot_z3n Package
Summary
MAL-2025-89339: Malicious code in outside_ocelot_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The outside_ocelot_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.
Vulnerability Detail
The vulnerability in the outside_ocelot_z3n package originates from its association with the tea.xyz token reward campaign. This campaign has led to the creation of numerous malicious packages that contain scripts (such as auto.js, autopublish.js) designed to modify the package.json file. These modifications include removing private flags, changing version numbers, and generating random package names, which can lead to the continuous republishing of these variants. The ramifications of this vulnerability include compromised package integrity, potential exposure of sensitive data, and a polluted npm registry, making it difficult for developers to find trustworthy packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall outside_ocelot_z3nIf 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 outside_ocelot_z3n package from your project if it is not essential. You can do this by executing the following command: npm uninstall outside_ocelot_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json file for any vulnerabilities in real-time.
Conclusion
The outside_ocelot_z3n package has been identified as containing malicious code that can compromise the integrity of your project. It is crucial to take immediate action by updating or removing the package to protect your application from potential risks. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for outside_ocelot_z3n →
FAQ
The outside_ocelot_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to compromised package integrity, potential data exposure, and pollution of the npm registry, making it difficult to find trustworthy packages.
If you are using the outside_ocelot_z3n package, you should update it to the latest patched version or remove it from your project.
You can use Vulert, which monitors your package-lock.json file for open-source 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 any signup.
