Critical Malicious Code Vulnerability in eslint-config-nitpicky Package
Summary
MAL-2025-190960: Malicious code in eslint-config-nitpicky (npm). Affects eslint-config-nitpicky versions 4.0.1. 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
eslint-config-nitpicky is an npm package designed to enforce strict coding standards and best practices for JavaScript projects. It helps developers maintain code quality by providing a set of predefined ESLint configurations. However, a recent discovery has revealed that this package contains malicious code, posing significant security risks to any system using it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the eslint-config-nitpicky package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it embeds harmful functionalities within the software. Users are advised to treat any system with this package as fully compromised, as the removal of the package may not eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eslint-config-nitpickyIf 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 eslint-config-nitpicky package altogether and consider using alternative ESLint configurations that do not pose security risks. Additionally, ensure that your codebase is regularly scanned for vulnerabilities using tools like Vulert.
Conclusion
The discovery of malicious code in the eslint-config-nitpicky package poses a serious threat to users. Immediate action is required to uninstall the package and secure any compromised systems. Regular monitoring and updates are essential to maintain the security of your development environment.
See every vulnerability recorded for eslint-config-nitpicky →
FAQ
You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Currently, there is no patched version available, so the best course of action is to uninstall the package.
Keeping the package installed can lead to unauthorized access to sensitive information and full compromise of your system.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.
