Malicious Code Detected in essential_stork_z3n: npm Package Vulnerability
Summary
MAL-2025-94290: Malicious code in essential_stork_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 essential_stork_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 and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the essential_stork_z3n package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, leading to pollution of the npm registry. This not only compromises the integrity of the registry but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall essential_stork_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 file to monitor dependencies. Ensure that you do not include essential_stork_z3n in your project dependencies. You can also use tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The essential_stork_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to remove this package and monitor for vulnerabilities to maintain the integrity of your software. Utilizing tools like Vulert can aid in real-time monitoring and alerting for such vulnerabilities.
See every vulnerability recorded for essential_stork_z3n →
FAQ
The essential_stork_z3n package is an npm package that has been identified as part of a malicious campaign aimed at flooding the npm registry.
The malicious code can compromise the integrity of your application by modifying package.json files and introducing potentially harmful dependencies.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
You should uninstall the package immediately using 'npm uninstall essential_stork_z3n' and check for any dependencies that may have been affected.
Yes, Vulert provides a service that uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software.
