Malicious Code Detected in @zalastax/nolb-graphqlp: A Critical Security Concern
Summary
MAL-2025-11790: Malicious code in @zalastax/nolb-graphqlp (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 package @zalastax/nolb-graphqlp is an npm library designed for GraphQL applications, providing functionalities that facilitate the integration of GraphQL with various back-end services. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-graphqlp package. This code can lead to unauthorized access, data breaches, or exploitation of the application environment. The malicious nature of this code can compromise the integrity and confidentiality of the data handled by applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-graphqlpIf 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, consider replacing the functionality provided by @zalastax/nolb-graphqlp with alternative libraries that do not have known vulnerabilities. Ensure to thoroughly review the alternatives for security and compatibility.
Conclusion
The discovery of malicious code in the @zalastax/nolb-graphqlp package highlights the importance of maintaining secure dependencies in software development. It is crucial to take immediate action to remove the affected package and monitor for any potential impacts on your applications.
See every vulnerability recorded for @zalastax/nolb-graphqlp →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and compromise application security.
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.
Consider implementing security measures such as access controls and monitoring to mitigate risks until you can remove the package.
While specific exploits have not been detailed, the presence of malicious code suggests potential for various attacks, including data theft and system compromise.
Yes, you can report vulnerabilities to the maintainers of the package or through platforms that track open-source vulnerabilities.
