Malicious Code Injection in systematic_falcon_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-109438: Malicious code in systematic_falcon_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 'systematic_falcon_z3n' is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for token rewards, posing a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'systematic_falcon_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages and projects that rely on npm. The malicious scripts included in the package (such as auto.js and autopublish.js) automate this harmful behavior, making it difficult for developers to detect and mitigate the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall systematic_falcon_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 workaround, you can avoid using the 'systematic_falcon_z3n' package altogether. If it is already included in your project, remove it by running the command: npm uninstall systematic_falcon_z3n. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The 'systematic_falcon_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for systematic_falcon_z3n →
FAQ
The vulnerability can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially compromising your project.
You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should uninstall the package immediately using the command: npm uninstall systematic_falcon_z3n to mitigate any risks.
Currently, there are no patches available for 'systematic_falcon_z3n'. The best course of action is to remove the package entirely.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, helping you maintain the security of your software.
