Malicious Code Injection in then_stork_z3n Package: npm Vulnerability
Summary
MAL-2025-109585: Malicious code in then_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 then_stork_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for tea protocol token rewards. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the then_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 continuous republishing of these variants pollutes the npm registry, potentially leading to security risks for developers who unknowingly use these compromised packages. The malicious behavior can result in unauthorized access to sensitive information and the proliferation of unreliable software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall then_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 then_stork_z3n package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The then_stork_z3n package poses a significant security risk due to its embedded malicious code that alters package metadata and floods the npm registry with unreliable packages. It is essential for developers to remove this package and monitor their dependencies closely to maintain the integrity of their projects.
See every vulnerability recorded for then_stork_z3n →
FAQ
The then_stork_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.
The malicious code modifies your package.json file, removes private flags, and can lead to the publication of unreliable packages, potentially compromising your project's security.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you have installed the then_stork_z3n package, you should uninstall it immediately using the command 'npm uninstall then_stork_z3n' and review your project for any other compromised packages.
To prevent similar vulnerabilities, regularly update your dependencies, monitor your package-lock.json file for unauthorized changes, and utilize tools like Vulert for real-time vulnerability alerts.
