Malicious Code Injection in conservation_carp_z3n Package: A Threat to npm Users
Summary
MAL-2025-93730: Malicious code in conservation_carp_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_carp_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 npm's publishing system. It contains scripts that automatically generate and publish derivative packages with altered names and metadata, potentially harming developers' reputations and polluting the npm registry.
Vulnerability Detail
The vulnerability stems from the malicious code embedded in the conservation_carp_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores through the tea.xyz token reward campaign, leading to a polluted npm registry and potential security risks for users who unknowingly install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall conservation_carp_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, avoid using the conservation_carp_z3n package and refrain from installing any packages that appear to be part of the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure no malicious packages are included.
Conclusion
The conservation_carp_z3n package poses a significant threat due to its malicious code that alters package metadata and inflates developer reputation scores. It is essential to remove this package and monitor your dependencies for security vulnerabilities. Utilizing tools like Vulert can help maintain the integrity of your projects.
See every vulnerability recorded for conservation_carp_z3n →
FAQ
It 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 installation of malicious code, which may compromise your project's integrity and security.
You should uninstall the conservation_carp_z3n package immediately and check for any other potentially malicious packages in your project.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
