Malicious Code Injection in conservation_ox_z3n: A Threat to npm Packages
Summary
MAL-2025-100863: Malicious code in conservation_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package conservation_ox_z3n is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of code among developers. However, this package has been identified as malicious, participating in a campaign that floods the npm registry with harmful derivatives, thereby compromising the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in conservation_ox_z3n stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. This package generates random names for derivative packages, which are then published to inflate developer reputation scores for token rewards. The malicious payload can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conservation_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 temporary workaround, you can avoid using the conservation_ox_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The conservation_ox_z3n package poses a significant threat due to its malicious nature, which can compromise the security of applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for conservation_ox_z3n →
FAQ
conservation_ox_z3n is an npm package that has been identified as malicious, involved in a campaign to flood the npm registry with harmful derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should uninstall the conservation_ox_z3n package immediately and look for alternative packages to replace its functionality.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
