Malicious Code Detected in @zalastax/nolb-node-sj Package

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

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12684: Malicious code in @zalastax/nolb-node-sj (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-node-sj package is an npm library designed for specific node.js functionalities. It is utilized in various applications for its intended features. However, it has been identified to contain malicious code, posing a significant risk to users and their applications. This vulnerability can lead to unauthorized access or data manipulation.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-node-sj package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can potentially allow attackers to execute harmful operations, leading to data breaches or system integrity issues. The malicious nature of this vulnerability was confirmed by Amazon Inspector, highlighting the need for immediate action.

How To Fix

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

npm uninstall @zalastax/nolb-node-sj

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 removing the @zalastax/nolb-node-sj package from your project until a patched version is released. You can do this by executing: npm uninstall @zalastax/nolb-node-sj.

Conclusion

The @zalastax/nolb-node-sj package has been found to contain malicious code, posing a significant risk to applications that utilize it. Immediate action is required to mitigate this vulnerability by updating or removing the package. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions within applications, potentially leading to 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 needing to sign up.

Consider removing the package from your project as a temporary measure until a secure version is available.

The vulnerability was identified by Amazon Inspector, a security tool that helps in detecting such issues.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to their latest versions.

How To Fix

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

npm uninstall @zalastax/nolb-node-sj

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