Malicious Code Detected in @zalastax/nolb-graphql-u Package
Summary
MAL-2025-11769: Malicious code in @zalastax/nolb-graphql-u (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-graphql-u package is an npm library designed for integrating GraphQL functionalities into applications. It is utilized for building APIs that can efficiently handle queries and mutations. However, this package has been identified as containing malicious code, posing significant security risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-graphql-u package stems from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities, making it imperative for users to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-graphql-uIf 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, consider using alternative packages that provide similar functionalities without the associated risks. Review your application dependencies and remove any instances of @zalastax/nolb-graphql-u until a secure version is confirmed.
Conclusion
The discovery of malicious code in the @zalastax/nolb-graphql-u package highlights the importance of monitoring dependencies for vulnerabilities. Users are urged to remove the affected package and consider alternatives while staying informed about updates and patches.
See every vulnerability recorded for @zalastax/nolb-graphql-u →
FAQ
The malicious code can lead to unauthorized access and potential data breaches, compromising application security.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
If no alternatives are available, consider isolating the affected functionality or implementing custom solutions until a secure package is found.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.
Failing to address this vulnerability can lead to severe security breaches, data loss, and damage to your application's reputation.
