Malicious Code Detected in @zalastax/nolb-node-red-ca Package

@zalastax/nolb-node-red-ca Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12650: Malicious code in @zalastax/nolb-node-red-ca (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-node-red-ca package is a Node-RED node designed for specific functionalities within the Node-RED ecosystem. It allows developers to integrate various services seamlessly. However, this package has been identified to contain malicious code, posing a significant risk to users who incorporate it into their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-node-red-ca package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, 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-node-red-ca

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, users can temporarily disable the functionalities provided by the @zalastax/nolb-node-red-ca package until a secure version is released. Additionally, consider using alternative packages that offer similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-node-red-ca package poses a serious threat to users. Immediate action is required to mitigate risks, including removing the 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-node-red-ca →

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 to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If you have installed the package, it is recommended to remove it immediately and look for alternative solutions.

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

It is uncertain at this time. Users should monitor the package repository for any updates or patches.

How To Fix

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

npm uninstall @zalastax/nolb-node-red-ca

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