Malicious Code Detected in @zalastax/nolb-nodejsa Package

@zalastax/nolb-nodejsa Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12774: Malicious code in @zalastax/nolb-nodejsa (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @zalastax/nolb-nodejsa package is an npm library designed for Node.js applications, providing various functionalities for developers. However, it has been identified to contain malicious code, posing significant risks to users who integrate it into their projects. The package's primary attributes include ease of use and integration, but its security flaws undermine these benefits.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-nodejsa 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 harmful actions within the affected systems. The issue was introduced in version 0 and has not been resolved, making it critical for users to take immediate action.

How To Fix

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

npm uninstall @zalastax/nolb-nodejsa

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 workaround, consider using alternative packages that provide similar functionalities without the associated risks. Always review package dependencies and their security status before integration.

Conclusion

The @zalastax/nolb-nodejsa package contains malicious code that poses significant security risks to applications. Users are advised to remove the package and monitor for updates. Utilizing tools like Vulert can help ensure ongoing security by identifying vulnerabilities in real-time.

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

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Currently, there is no patched version available for the @zalastax/nolb-nodejsa package. Users should remove it from their projects.

Remove the package immediately and consider using alternative libraries that do not pose security risks.

Vulert uses the package-lock.json file to monitor and alert users about open-source vulnerabilities without requiring code access or installation.

How To Fix

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

npm uninstall @zalastax/nolb-nodejsa

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