Critical Malicious Code Vulnerability in @saazkira/eslint-config Package
Summary
MAL-2026-17835: Malicious code in @saazkira/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 @saazkira/eslint-config package is an npm package designed to provide a set of ESLint configurations for JavaScript projects. It aims to streamline the process of setting up linting rules, ensuring code quality and consistency across projects. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @saazkira/eslint-config package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity, making it critical for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @saazkira/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
There are no effective workarounds for this vulnerability due to the nature of the malicious code. The only recommended action is to remove the package entirely and secure the system.
Conclusion
The @saazkira/eslint-config package contains malicious code that poses a significant security threat. Users are urged to uninstall the package immediately and take necessary precautions to secure their systems. Regular monitoring for vulnerabilities using tools like Vulert can help prevent future risks.
See every vulnerability recorded for @saazkira/eslint-config →
FAQ
You should immediately uninstall the package and rotate any sensitive information stored on your system.
You can uninstall the package by running the command: npm uninstall @saazkira/eslint-config in your terminal.
No, there is currently no patched version available for the @saazkira/eslint-config package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to your system, potential data breaches, and loss of sensitive information.
