Malicious Code Injection in local_gecko_z3n Package
Summary
MAL-2025-98794: Malicious code in local_gecko_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 local_gecko_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is often utilized in various applications to manage dependencies and facilitate package management. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the local_gecko_z3n package originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, thereby inflating developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall local_gecko_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 local_gecko_z3n package and replace it with a reputable alternative that provides similar functionality without the associated risks. Always validate the source of any package before integrating it into your project.
Conclusion
The local_gecko_z3n package poses a significant security risk due to its malicious code designed to exploit npm's publishing capabilities. It is crucial for developers to remove this package from their projects and monitor their dependencies regularly to maintain application integrity. Utilizing tools like Vulert can help in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for local_gecko_z3n →
FAQ
The local_gecko_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code can modify your package.json file, remove private flags, and continuously publish variants, potentially compromising your application's integrity.
If you have installed the local_gecko_z3n package, you should uninstall it immediately using the command npm uninstall local_gecko_z3n.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
Yes, consider using reputable packages that offer similar functionality but do not have known vulnerabilities.
