Malicious Code Injection in condemned_bison_z3n Package
Summary
MAL-2025-100819: Malicious code in condemned_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 condemned_bison_z3n package is part of the npm ecosystem, typically used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers' reputations and polluting the registry.
Vulnerability Detail
The vulnerability in the condemned_bison_z3n package stems from its malicious code, which is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious payload can lead to significant issues, including the proliferation of unwanted packages in the npm registry and potential security risks for applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall condemned_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 prevent the installation of the condemned_bison_z3n package by using npm's package-lock.json file to lock your dependencies. This will ensure that the malicious package is not included in future installations. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.
Conclusion
The condemned_bison_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help safeguard your applications from such threats.
See every vulnerability recorded for condemned_bison_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious code.
The code modifies your package.json, removes private flags, and can lead to the creation of unwanted packages in the npm registry.
You should uninstall the condemned_bison_z3n package immediately using npm uninstall condemned_bison_z3n.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.
