Malicious Code Injection in close_ox_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-93586: Malicious code in close_ox_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 close_ox_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 for token rewards, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the close_ox_z3n package originates from its involvement in the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially leading to security risks for developers who unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall close_ox_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 workaround, you can avoid using the close_ox_z3n package entirely. If it is already included in your project, remove it by running: npm uninstall close_ox_z3n. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The close_ox_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package metadata and floods the registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security.
See every vulnerability recorded for close_ox_z3n →
FAQ
The close_ox_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the close_ox_z3n package immediately and monitor your project for any other vulnerabilities.
You can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in your software using just package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
