Malicious Code Injection in scared_camel_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-108405: Malicious code in scared_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 'scared_camel_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, undermining the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'scared_camel_z3n' stems from its association with a malicious campaign that 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 for token rewards, leading to a polluted npm registry. The malicious payload can compromise the security of applications relying on this package, potentially allowing unauthorized access or manipulation of data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scared_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 temporary workaround, you can avoid using the 'scared_camel_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The 'scared_camel_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications by removing affected packages and monitoring for updates.
See every vulnerability recorded for scared_camel_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and functionality.
Remove the 'scared_camel_z3n' package from your project immediately and monitor for any updates or patches from the npm registry.
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.
