Malicious Code Injection in conservation_asp_z3n Package
Summary
MAL-2025-100862: Malicious code in conservation_asp_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 conservation_asp_z3n package is part of the npm ecosystem, primarily used for various JavaScript applications. It has been identified as part of a broader malicious campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the conservation_asp_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers who unknowingly use these packages. The origin of this issue is linked to a token reward campaign that incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conservation_asp_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 conservation_asp_z3n package altogether. If it is already included in your project, remove it by executing: npm uninstall conservation_asp_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The conservation_asp_z3n package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help mitigate potential threats from malicious packages.
See every vulnerability recorded for conservation_asp_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The malicious code can modify your package.json, remove private flags, and publish unauthorized package variants, potentially compromising your project's integrity.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the conservation_asp_z3n package immediately using the command: npm uninstall conservation_asp_z3n.
Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time, providing alerts for any issues.
