Malicious Code Detected in @zalastax/nolb-graph4 Package

@zalastax/nolb-graph4 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-11740: Malicious code in @zalastax/nolb-graph4 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @zalastax/nolb-graph4 package is an npm library designed for graph-related functionalities. It is utilized by developers to create and manipulate graph structures in JavaScript applications. However, this package has been identified to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-graph4 package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other harmful effects. The malicious nature of the code was confirmed by security researchers, highlighting the importance of vigilance when using third-party libraries.

How To Fix

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

npm uninstall @zalastax/nolb-graph4

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 using alternative packages that provide similar functionalities without the associated risks. Review your project's dependencies and replace @zalastax/nolb-graph4 with a trusted library.

Conclusion

The discovery of malicious code in the @zalastax/nolb-graph4 package underscores the importance of security in software development. Users are urged to remove the package and consider alternatives while staying informed about updates and patches. Utilizing tools like Vulert can help maintain the integrity of your applications.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Immediately remove the @zalastax/nolb-graph4 package from your project and consider using alternative libraries.

Currently, there is no patched version available. It is advisable to remove the package until a secure version is released.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and always review package repositories before integrating third-party libraries.

How To Fix

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

npm uninstall @zalastax/nolb-graph4

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