Critical Malicious Code Vulnerability in barebones-css Package
Summary
MAL-2025-191070: Malicious code in barebones-css (npm). Affects barebones-css versions 1.1.3 – 1.1.4. 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
barebones-css is a lightweight CSS framework designed to provide a minimalistic approach to styling web applications. It aims to simplify the development process by offering essential styling features without the bloat of larger frameworks. However, it has been found to contain malicious code that compromises the security of any system where it is installed.
Vulnerability Detail
The vulnerability originates from a malicious code embedded within the barebones-css package, identified as GHSA-27gg-rj6x-rpc2. Any computer that has this package installed is considered fully compromised, allowing unauthorized access to sensitive information such as secrets and keys. The presence of this malicious code poses a significant risk, as it may lead to data breaches and unauthorized control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall barebones-cssIf 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 only safe action is to remove the package entirely from your project and system.
Conclusion
The barebones-css package has been identified as containing malicious code that compromises the security of systems where it is installed. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of your dependencies using tools like Vulert can help prevent future vulnerabilities.
See every vulnerability recorded for barebones-css →
FAQ
Immediately uninstall the package using npm uninstall barebones-css and rotate any sensitive information that may have been compromised.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Keeping the barebones-css package poses significant risks, including unauthorized access to sensitive data and potential control over your system by malicious actors.
No, there is currently no patched version available. The recommendation is to remove the package entirely.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.
