Critical Malicious Code Vulnerability in @badzz88/eslint-config Package
Summary
MAL-2026-17819: Malicious code in @badzz88/eslint-config (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 @badzz88/eslint-config package is a configuration tool for ESLint, a popular JavaScript linter that helps developers identify and fix problems in their JavaScript code. This package is designed to streamline the setup of ESLint with predefined rules and settings. However, it has been compromised, containing malicious code that poses significant security risks to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @badzz88/eslint-config package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionalities that can lead to severe security breaches. Users are advised to treat any system running this package as compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @badzz88/eslint-configIf 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
Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and securing the system. Users should ensure that they have removed the package using the command: npm uninstall @badzz88/eslint-config.
Conclusion
The @badzz88/eslint-config package has been identified as containing malicious code that compromises systems where it is installed. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for @badzz88/eslint-config →
FAQ
Immediately uninstall the package using npm uninstall @badzz88/eslint-config and rotate any sensitive information stored on the affected system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
Leaving the package installed can lead to unauthorized access to sensitive data, potential data breaches, and full system compromise.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file, providing real-time insights into potential risks.
