Malicious Code Injection in broken_scorpion_z3n Package: A Threat to npm Ecosystem
Summary
MAL-2025-100134: Malicious code in broken_scorpion_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_scorpion_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate token rewards, but it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in the broken_scorpion_z3n package stems from its inclusion in a malicious campaign that employs scripts to auto-generate and publish derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further vulnerabilities and security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall broken_scorpion_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 broken_scorpion_z3n package altogether. If it is already in use, consider replacing it with a reputable alternative that does not have known vulnerabilities.
Conclusion
The broken_scorpion_z3n package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain application security.
See every vulnerability recorded for broken_scorpion_z3n →
FAQ
It is an npm package associated with a token reward campaign that has been compromised to include malicious code.
Using the compromised package can lead to the injection of malicious scripts, potentially compromising your application's security.
You should remove the broken_scorpion_z3n package from your project and monitor for any updates or patches.
You can use tools like Vulert, which monitors your package-lock.json file 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.
