Malicious Code Injection in broken_bison_z3n Package
Summary
MAL-2025-98637: Malicious code in broken_bison_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 broken_bison_z3n package is part of the npm ecosystem, often used for various JavaScript applications. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its primary functionality is compromised by the presence of scripts that automate the generation and publication of these packages, which can lead to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in the broken_bison_z3n package originates from its association with the tea.xyz token reward campaign. This campaign employs malicious scripts (auto.js, autopublish.js, etc.) that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants can pollute the npm registry, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall broken_bison_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 remove the broken_bison_z3n package from your project by executing: npm uninstall broken_bison_z3n. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The broken_bison_z3n package poses a significant security risk due to its association with malicious scripts that manipulate package metadata and republish variants. It is essential for developers to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for broken_bison_z3n →
FAQ
The broken_bison_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the publication of derivative packages.
This vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of your application by introducing malicious code.
If you are using broken_bison_z3n, it is crucial to update to a patched version or remove the package entirely until a secure version is released.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.
To prevent similar vulnerabilities, regularly audit your dependencies, keep them updated, and utilize tools like Vulert for real-time monitoring of open-source vulnerabilities.
