Malicious Code Detected in @zalastax/nolb-node-si - Security Alert

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12683: Malicious code in @zalastax/nolb-node-si (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 package @zalastax/nolb-node-si is an npm package designed for specific functionalities within Node.js applications. It is utilized by developers for its intended features, but it has been identified as containing malicious code that poses a security risk to users. This vulnerability can compromise the integrity of applications that depend on this package.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-node-si package stems from the inclusion of malicious code. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that utilize this package. 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-si

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 remove the @zalastax/nolb-node-si package from their project until a secure version is released. This can be done by executing the following command: npm uninstall @zalastax/nolb-node-si

Conclusion

The discovery of malicious code in the @zalastax/nolb-node-si package poses significant risks to users. It is crucial to take immediate action by removing the package or replacing it with a secure alternative. Regular monitoring through tools like Vulert can help maintain the security of your applications.

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

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or control over the application.

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. Users are advised to remove the package until a fix is released.

If immediate removal is not possible, ensure to monitor your application closely for any suspicious activity and consider implementing additional security measures.

Vulert uses the package-lock.json file to monitor and alert users in real-time for any open-source vulnerabilities, providing an easy way to stay informed.

How To Fix

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

npm uninstall @zalastax/nolb-node-si

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