Critical Malicious Code Vulnerability in lint-builder Package
Summary
MAL-2026-1936: Malicious code in lint-builder (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
lint-builder is an npm package designed to assist developers in managing and automating linting tasks within their JavaScript projects. It is widely used for ensuring code quality and consistency. However, this package has been found to contain malicious code that compromises the security of any system where it is installed, making it a significant threat to developers and their projects.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the lint-builder 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 this code is classified under CWE-506, indicating that it poses a serious risk to users and their systems. Users are advised to treat any system with this package as compromised and take immediate action to mitigate potential damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lint-builderIf 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. The best course of action is to remove the package entirely and ensure that all sensitive information is secured.
Conclusion
The discovery of malicious code within the lint-builder package poses a serious threat to users and their systems. Immediate action is required to remove the package and secure sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for lint-builder →
FAQ
Immediately remove the lint-builder package from your system and rotate any sensitive information stored on that machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
While many npm packages are safe, it is essential to review and monitor all dependencies regularly for vulnerabilities.
