Malicious Code Injection in stormy_swordtail_z3n: A Threat to npm Packages
Summary
MAL-2025-109154: Malicious code in stormy_swordtail_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 package stormy_swordtail_z3n 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. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in stormy_swordtail_z3n originates from its association with the tea.xyz token reward campaign, which utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. This can lead to developers inadvertently using compromised packages, which may contain further vulnerabilities or malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stormy_swordtail_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 stormy_swordtail_z3n package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure that no malicious packages are included in your project.
Conclusion
The stormy_swordtail_z3n package poses a significant risk due to its malicious nature and the potential for widespread impact on the npm ecosystem. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their projects from malicious attacks.
See every vulnerability recorded for stormy_swordtail_z3n →
FAQ
stormy_swordtail_z3n is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.
Using the stormy_swordtail_z3n package can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should remove the stormy_swordtail_z3n package from your project immediately and check for any other compromised packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Yes, tools like npm audit can help you identify vulnerabilities in your dependencies, and services like Vulert provide real-time monitoring for open-source vulnerabilities.
