Malicious Code Injection in then_ocelot_z3n Package - npm Vulnerability
Summary
MAL-2025-96983: Malicious code in then_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 then_ocelot_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the then_ocelot_z3n package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This can result in reputational damage for developers and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall then_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 then_ocelot_z3n package from your project by executing 'npm uninstall then_ocelot_z3n'. This will prevent the malicious code from executing until a secure version is available.
Conclusion
The then_ocelot_z3n package has been identified as containing malicious code that compromises its integrity and poses security risks. It is crucial for developers to take immediate action by uninstalling the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.
See every vulnerability recorded for then_ocelot_z3n →
FAQ
The then_ocelot_z3n package is an npm package that has been identified as containing malicious code aimed at manipulating package metadata.
The malicious code can alter your package.json file, potentially leading to security vulnerabilities and reputational damage by flooding the npm registry with harmful packages.
You should immediately uninstall the then_ocelot_z3n package and check for any updates or patches that may be released to address this vulnerability.
Yes, you can use Vulert to monitor your application for open-source vulnerabilities in real-time. It analyzes your package-lock.json file without requiring code access.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
