Malicious Code Injection in valid_crocodile_z3n Package
Summary
MAL-2025-91657: Malicious code in valid_crocodile_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 valid_crocodile_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the valid_crocodile_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants pollutes the npm registry, potentially leading to dependency confusion and exploitation by malicious actors. The impact includes compromised project integrity and increased risk of supply chain attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall valid_crocodile_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include valid_crocodile_z3n in its dependencies. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your project without requiring code access.
Conclusion
The valid_crocodile_z3n package poses a significant security risk due to its malicious code that modifies project files and repopulates the npm registry with harmful variants. It is essential to remove this package and monitor your dependencies to maintain project integrity.
See every vulnerability recorded for valid_crocodile_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.
The malicious code modifies your package.json, potentially leading to dependency confusion and increased risk of supply chain attacks.
You should uninstall the valid_crocodile_z3n package immediately and check for any dependencies that may rely on it.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only install packages from trusted sources.
