Malicious Code Injection in patient_stork_z3n Package - npm Vulnerability
Summary
MAL-2025-122451: Malicious code in patient_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 patient_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 of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability poses a significant risk to developers and users relying on this package for their projects.
Vulnerability Detail
The vulnerability in the patient_stork_z3n package originates from its association with the tea.xyz token reward campaign. It includes malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to security risks for developers who unknowingly use these compromised packages. The malicious payload can also affect the integrity of applications relying on this package, potentially introducing further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall patient_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 patient_stork_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The patient_stork_z3n package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and applications. It is essential to remove this package and monitor your dependencies for vulnerabilities to maintain the security and integrity of your projects.
See every vulnerability recorded for patient_stork_z3n →
FAQ
The patient_stork_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
This vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json and republishing variants that may contain further vulnerabilities.
You should uninstall the patient_stork_z3n package immediately and check for any other compromised packages in your project.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.