Malicious Code Injection in original_stork_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-106800: Malicious code in original_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 original_stork_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that automate the generation and publishing of derivative packages, potentially leading to a polluted npm registry and inflated developer reputation scores.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the original_stork_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, which can lead to a significant pollution of the npm registry and compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall original_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 avoid using the original_stork_z3n package and any of its derivatives. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.
Conclusion
The original_stork_z3n package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and repopulates the registry with harmful variants. It is essential to remove this package and monitor your dependencies to maintain the integrity of your projects.
See every vulnerability recorded for original_stork_z3n →
FAQ
The original_stork_z3n package is an npm package that has been identified as malicious, associated with a token reward campaign that floods the npm registry with harmful packages.
The malicious code can modify your package.json file, remove private flags, and continuously republish variants, which can lead to a polluted npm registry and compromise your project's integrity.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.
You should immediately remove the original_stork_z3n package from your project and check for any updates or patches that may address this vulnerability.
Regularly audit your dependencies using tools like npm audit and stay informed about vulnerabilities in the packages you use. Consider using Vulert for real-time monitoring.
