Malicious Code Vulnerability in vulnerable_camel_z3n Package
Summary
MAL-2025-110636: Malicious code in vulnerable_camel_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 vulnerable_camel_z3n package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of autopublish scripts that modify package metadata and continuously republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the vulnerable_camel_z3n package, which is part of a broader campaign that floods the npm ecosystem with harmful packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to significant ramifications, including the potential for developers to unknowingly install compromised packages, which can further propagate the malicious code and affect their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vulnerable_camel_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The vulnerable_camel_z3n package poses a significant risk due to its malicious behavior, which can compromise the integrity of applications using it. It is crucial to remove this package and monitor your projects for vulnerabilities to maintain security.
See every vulnerability recorded for vulnerable_camel_z3n →
FAQ
The vulnerable_camel_z3n package is an npm package identified as part of a malicious campaign that modifies package metadata and floods the npm registry with harmful derivatives.
If your application uses the vulnerable_camel_z3n package, it may inadvertently install malicious code that can compromise its security and functionality.
You should uninstall the vulnerable_camel_z3n package immediately and monitor your project for any further vulnerabilities.
Yes, you can use tools like Vulert to monitor your dependencies for vulnerabilities in real-time and ensure that you are alerted to any issues as they arise.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
