Malicious Code Detected in @zalastax/nolb-css-d Package
Summary
MAL-2025-11047: Malicious code in @zalastax/nolb-css-d (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 @zalastax/nolb-css-d package is an npm library designed for styling web applications. It provides a set of CSS utilities aimed at enhancing the visual aspects of web projects. However, it has been identified to contain malicious code, posing a significant risk to users who integrate it into their applications.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-css-d package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-css-dIf 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 measure, you can avoid using the @zalastax/nolb-css-d package until a secure version is released. Consider using alternative CSS libraries that do not have known vulnerabilities.
Conclusion
The @zalastax/nolb-css-d package has been found to contain malicious code, posing a serious risk to applications that use it. It is essential to remove this package and monitor for any updates or alternatives to ensure the security of your projects.
See every vulnerability recorded for @zalastax/nolb-css-d →
FAQ
The malicious code can lead to security vulnerabilities, including unauthorized access to sensitive data.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Immediately remove the package from your project and monitor for any updates or patches that may address the vulnerability.
Yes, consider using other well-known CSS libraries that are actively maintained and have a good security track record.
Regularly check your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
