Malicious Code Injection in coming_swift_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-93646: Malicious code in coming_swift_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 'coming_swift_z3n' is part of the npm ecosystem, which is widely used for managing JavaScript packages. 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 designed to manipulate and republish derivative packages, thereby inflating developer reputation scores for token rewards. The presence of such malicious code poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'coming_swift_z3n' originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This behavior can lead to security risks, including the potential for unauthorized access to sensitive data and the compromise of application integrity. The malicious payload is designed to exploit the npm ecosystem, making it imperative for developers to be vigilant about the packages they use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall coming_swift_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 'coming_swift_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'coming_swift_z3n' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and republish variants. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for coming_swift_z3n →
FAQ
The 'coming_swift_z3n' package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
This vulnerability can compromise your application's integrity by introducing malicious code that may lead to unauthorized access or data breaches.
If you have installed 'coming_swift_z3n', you should uninstall it immediately using 'npm uninstall coming_swift_z3n' and monitor your project for any other vulnerabilities.
To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and employ tools like Vulert to monitor for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
