Malicious Code Injection in coming_ocelot_z3n Package
Summary
MAL-2025-98649: Malicious code in coming_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 coming_ocelot_z3n package 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 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 security risks for developers and users alike.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the coming_ocelot_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The primary goal is to continuously republish these variants, polluting the npm registry and potentially compromising other packages. The origin of this vulnerability is linked to a token reward campaign that incentivizes the creation of such malicious packages, posing a risk to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall coming_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 measure, you can avoid using the coming_ocelot_z3n package until a secure version is released. Additionally, you may want to implement strict package management practices to monitor and audit dependencies regularly.
Conclusion
The coming_ocelot_z3n package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is crucial for developers to take immediate action to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for coming_ocelot_z3n →
FAQ
The coming_ocelot_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The malicious code can alter your package.json file, remove private flags, and republish variants, which can compromise the integrity of your project and lead to security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file on the Vulert playground, you can determine if your application is affected by this vulnerability.
You should remove the coming_ocelot_z3n package from your project and update to a patched version if available. If no patch exists, consider using a trusted alternative.
Implement strict package management practices, regularly audit dependencies, and stay informed about vulnerabilities in the packages you use.
