Malicious Code Vulnerability in lint-staged-custom Package
Summary
MAL-2025-6630: Malicious code in lint-staged-custom (npm). Affects lint-staged-custom versions 1.0.0. 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
lint-staged-custom is an npm package designed to run linters on pre-committed files, enhancing code quality and consistency in development workflows. However, this package has been identified with a serious vulnerability that allows for the execution of malicious code, potentially compromising the security of applications that utilize it.
Vulnerability Detail
The vulnerability identified as MAL-2025-6630 originates from a malicious version of the lint-staged-custom package (version 1.0.0). This version contains harmful code that can execute unauthorized actions within the user's environment. The ramifications of this vulnerability include data breaches, unauthorized access to sensitive information, and potential system compromise. Users of this package are at risk if they have installed the affected version, as it can lead to severe security incidents.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lint-staged-customIf 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 affected version of lint-staged-custom by removing it from your project. Use the following command to uninstall the package: npm uninstall lint-staged-custom. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The lint-staged-custom package has a critical vulnerability that poses significant security risks to applications using it. Users are advised to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor and manage open-source vulnerabilities effectively.
See every vulnerability recorded for lint-staged-custom →
FAQ
lint-staged-custom is an npm package that allows developers to run linters on files that are staged for commit, ensuring code quality.
You can use Vulert, a tool that monitors open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including this one.
If immediate updates are not feasible, consider removing the package and using alternative solutions until a secure version is available.
Detailed information about this vulnerability can be found on the ReversingLabs website and the GitHub repository for malicious packages.
Yes, you can use the Vulert playground to check if your application is affected by this vulnerability without requiring any code or installation.
