Critical Malicious Code Vulnerability in stylelint-recommended Package
Summary
MAL-2026-872: Malicious code in stylelint-recommended (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 stylelint-recommended package is a widely used npm module that provides a set of recommended rules for Stylelint, a modern CSS linter. It helps developers maintain consistent coding styles and catch errors in their CSS code. However, this package has been compromised, introducing a serious security risk to any system that has it installed.
Vulnerability Detail
The vulnerability stems from the presence of malicious code embedded within the stylelint-recommended 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 origin of this malicious code is linked to a known malware source, and it poses significant risks to the integrity and security of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stylelint-recommendedIf 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 workaround, ensure that you rotate all secrets and keys stored on the compromised computer from a different, secure machine. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The stylelint-recommended package has been compromised with malicious code, posing a significant security threat to any system that has it installed. Immediate action is required to remove the package and secure sensitive information. Regular monitoring of dependencies is essential to maintain security.
See every vulnerability recorded for stylelint-recommended →
FAQ
Immediately remove the stylelint-recommended package from your system and rotate any sensitive information stored on that machine.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Currently, there is no patched version available. It is recommended to remove the package entirely.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential further compromise of your system.
While many npm packages are safe, it is crucial to monitor and audit your dependencies regularly for vulnerabilities.
