Malicious Code Injection in binding_guineafowl_z3n Package
Summary
MAL-2025-93382: Malicious code in binding_guineafowl_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 binding_guineafowl_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. This package, like others in the campaign, is vulnerable to exploitation due to its inclusion of autopublish scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in the binding_guineafowl_z3n package stems from its malicious payload that modifies the package.json file. This payload removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is tied to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall binding_guineafowl_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 binding_guineafowl_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The binding_guineafowl_z3n package poses a significant security risk due to its malicious code that alters package metadata. It is essential for developers to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for binding_guineafowl_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the binding_guineafowl_z3n package immediately and check for any other potentially malicious packages in your project.
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 by this vulnerability without needing to sign up.
