Malicious Code Injection in maximum_crocodile_z3n: A Threat to npm Packages
Summary
MAL-2025-105674: Malicious code in maximum_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 package maximum_crocodile_z3n 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 the npm registry by flooding it with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which has been known to deploy autopublish scripts. These scripts are designed to automatically generate and publish derivative packages with randomized names, effectively inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential security risks for developers using these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall maximum_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 measure, you can avoid using the maximum_crocodile_z3n package and any packages that depend on it. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. 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 maximum_crocodile_z3n package poses a significant risk due to its malicious code that modifies package files and repopulates the npm registry with potentially harmful variants. It is crucial for developers to take immediate action to remove this package and monitor their projects for vulnerabilities.
See every vulnerability recorded for maximum_crocodile_z3n →
FAQ
maximum_crocodile_z3n is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.
You should uninstall the package immediately using the command npm uninstall maximum_crocodile_z3n and check for any dependencies that may rely on it.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
