Malicious Code Detected in @zalastax/nolb-disl Package

@zalastax/nolb-disl Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-11173: Malicious code in @zalastax/nolb-disl (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-disl package is an npm library designed for specific functionalities within JavaScript applications. It is used by developers to streamline certain processes, but it has been found to contain malicious code that poses a security risk to users. This vulnerability can lead to unauthorized access or manipulation of application data.

Vulnerability Detail

The vulnerability identified in the @zalastax/nolb-disl package is classified as malicious code. This code was intentionally introduced into the package, potentially allowing attackers to exploit the affected systems. The origin of this vulnerability is traced back to the package's version 0 and could lead to severe ramifications, including data breaches and compromised application integrity.

How To Fix

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

npm uninstall @zalastax/nolb-disl

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, you can remove the @zalastax/nolb-disl package from your project until a secure version is released. This can be done by executing the command: 'npm uninstall @zalastax/nolb-disl'.

Conclusion

The @zalastax/nolb-disl package has been identified with a serious vulnerability due to the presence of malicious code. Users are advised to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

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

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to application data and compromise the integrity of the software.

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.

If an immediate update is not possible, consider removing the package from your project as a temporary measure.

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

How To Fix

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

npm uninstall @zalastax/nolb-disl

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