Malicious Code Detected in variables.css Package - Security Risk Identified
Summary
MAL-2025-6966: Malicious code in variables.css (npm). Affects variables.css 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
The variables.css package is a popular npm library used for managing CSS variables in web development. It simplifies the process of defining and using CSS variables, making it easier for developers to maintain consistent styling across their applications. However, this package has been found to communicate with a domain associated with malicious activity, raising significant security concerns for users.
Vulnerability Detail
The vulnerability in the variables.css package originates from its communication with a domain linked to malicious activities. This could potentially expose users to security risks such as data breaches, unauthorized access, or the injection of harmful code into applications. The issue was introduced in version 1.0.0, and it is crucial for developers to be aware of the implications of using this compromised package in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall variables.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
As a temporary workaround, developers can avoid using the variables.css package until a secure version is released. Alternatively, consider using other CSS variable management libraries that do not have known vulnerabilities.
Conclusion
The discovery of malicious code in the variables.css package highlights the importance of vigilance in managing dependencies in software development. Developers should take immediate action to update or replace vulnerable packages to ensure the security of their applications.
See every vulnerability recorded for variables.css →
FAQ
The vulnerability involves the package communicating with a domain associated with malicious activity, posing security risks to users.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check your application without any signup.
It is advisable to update the package to the latest version or consider alternative libraries until a secure version is available.
Yes, you can temporarily avoid using the variables.css package and look for other libraries that offer similar functionality without the associated risks.
You can visit Vulert's website for real-time monitoring and alerts regarding open-source vulnerabilities in your software.
