Malicious Code Detected in @zalastax/nolb-nodebo Package

@zalastax/nolb-nodebo Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12765: Malicious code in @zalastax/nolb-nodebo (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-nodebo package is an npm library designed for specific functionalities within Node.js applications. It is utilized for various tasks in web development, but recent findings have revealed that it contains malicious code, posing a significant risk to users and their applications. This vulnerability can lead to unauthorized access or data breaches, making it critical for developers to address it promptly.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-nodebo package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially allow attackers to execute harmful actions, such as data theft or unauthorized access to sensitive information. The issue is particularly concerning as it affects all versions starting from the initial release, making it imperative for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall @zalastax/nolb-nodebo

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, users can avoid using the @zalastax/nolb-nodebo package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-nodebo package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action by uninstalling the affected package and monitoring for updates. Utilizing tools like Vulert can further enhance security by providing real-time alerts for vulnerabilities.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications using this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed the package, it is recommended to uninstall it immediately and monitor for any updates or patches from the maintainers.

Yes, consider using other npm packages that offer similar functionalities but do not have known vulnerabilities.

Regularly check for updates on your packages and use tools like Vulert to monitor your project for any vulnerabilities in real-time.

How To Fix

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

npm uninstall @zalastax/nolb-nodebo

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