Malicious Code Detected in @zalastax/nolb-nodebr Package

@zalastax/nolb-nodebr Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12767: Malicious code in @zalastax/nolb-nodebr (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-nodebr package is an npm library designed for Node.js applications, providing specific functionalities that developers can leverage in their projects. However, it has been identified to contain malicious code, posing a significant risk to users who incorporate it into their applications. This vulnerability can lead to unauthorized access, data breaches, or other malicious activities.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-nodebr package stems from the presence of malicious code that was intentionally introduced. This code can compromise the security of applications utilizing this package, potentially leading to data theft, unauthorized actions, or system damage. The malicious nature of the code makes it imperative for users to take immediate action to mitigate risks associated with its use.

How To Fix

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

npm uninstall @zalastax/nolb-nodebr

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 functionality without the associated risks. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The discovery of malicious code in the @zalastax/nolb-nodebr package highlights the importance of vigilance when using open-source libraries. Users are urged to remove the package immediately and explore alternatives to safeguard their applications.

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

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access or data breaches.

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.

Immediately uninstall the package using npm uninstall @zalastax/nolb-nodebr and consider using alternative packages.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

Currently, there is no patched version available. It is recommended to monitor the package repository for updates.

How To Fix

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

npm uninstall @zalastax/nolb-nodebr

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