Malicious Code Injection in planned_crocodile_z3n Package
Summary
MAL-2025-95903: Malicious code in planned_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 planned_crocodile_z3n package 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 primary functionality of this package is compromised due to the presence of malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the planned_crocodile_z3n package, which is associated with the tea.xyz token reward campaign. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a pollution of the npm registry with numerous derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall planned_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 avoid using the planned_crocodile_z3n package and any other packages that may have been published as part of the malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The planned_crocodile_z3n package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for planned_crocodile_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code can alter your package metadata, potentially leading to reputation damage and security vulnerabilities in your project.
You should uninstall the planned_crocodile_z3n package immediately using the command npm uninstall planned_crocodile_z3n.
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.
