Malicious Code Detected in @zalastax/nolb-node-b Package

@zalastax/nolb-node-b Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12595: Malicious code in @zalastax/nolb-node-b (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @zalastax/nolb-node-b package is an npm library designed for Node.js applications. It provides various functionalities that developers can utilize to enhance their applications. However, this package has been identified to contain malicious code, posing significant risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-node-b package stems from the inclusion of malicious code that could compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall @zalastax/nolb-node-b

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, you can avoid using the @zalastax/nolb-node-b package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-node-b package highlights the importance of vigilance when using open-source libraries. Users are advised to remove the package from their projects and seek alternatives to safeguard their applications from potential threats.

See every vulnerability recorded for @zalastax/nolb-node-b →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to systems, leading to data breaches or other harmful activities.

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.

It is crucial to remove the @zalastax/nolb-node-b package immediately and consider using alternative packages that do not pose security risks.

The best course of action is to avoid using the package altogether. If you must use it, ensure that you have robust security measures in place.

Currently, there is no patch available. It is essential to monitor the package repository for any updates regarding a fix.

How To Fix

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

npm uninstall @zalastax/nolb-node-b

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