Malicious Code Detected in @zalastax/nolb-graphqlb Package

@zalastax/nolb-graphqlb Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-11779: Malicious code in @zalastax/nolb-graphqlb (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The @zalastax/nolb-graphqlb package is an npm library designed for GraphQL-based applications, providing functionalities that facilitate the integration and management of GraphQL queries and mutations. However, it has been found to contain malicious code that poses a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-graphqlb package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other malicious activities, potentially affecting the integrity and confidentiality of user data. The issue was introduced in version 0 and has been flagged as a critical concern for developers relying on this package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zalastax/nolb-graphqlb

If 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 removing the @zalastax/nolb-graphqlb package from your project until a secure version is released. You can do this by executing: npm uninstall @zalastax/nolb-graphqlb.

Conclusion

The @zalastax/nolb-graphqlb package contains malicious code that poses a serious threat to applications using it. It is essential to act promptly by updating or removing the package to safeguard your application and user data.

See every vulnerability recorded for @zalastax/nolb-graphqlb →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.

It is crucial to check the package repository for any updates or patched versions of @zalastax/nolb-graphqlb.

Consider removing the package from your project as a temporary measure until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps in finding vulnerabilities in software packages.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @zalastax/nolb-graphqlb

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback