Malicious Code Vulnerability in worried_camel_z3n Package
Summary
MAL-2025-97413: Malicious code in worried_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 worried_camel_z3n package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants of itself, leading to potential security risks for users.
Vulnerability Detail
The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward initiative. It contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks from untrusted code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall worried_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 avoid using the worried_camel_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project dependencies using tools like Vulert to detect any vulnerabilities in real-time.
Conclusion
The worried_camel_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.
See every vulnerability recorded for worried_camel_z3n →
FAQ
The worried_camel_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
If you have installed the worried_camel_z3n package, it is recommended to remove it immediately and monitor your application for any unusual behavior.
Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
