Malicious Code Injection in structural_gecko_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-96821: Malicious code in structural_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 package 'structural_gecko_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 for token rewards, posing significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in 'structural_gecko_z3n' originates from its association with the tea.xyz token reward campaign. It contains malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent projects. The malicious payload can result in unauthorized access to sensitive information and can disrupt the normal functioning of applications relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall structural_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 'structural_gecko_z3n' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'structural_gecko_z3n' package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for structural_gecko_z3n →
FAQ
'structural_gecko_z3n' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's integrity and security.
You should uninstall the 'structural_gecko_z3n' package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
