Critical Malicious Code Vulnerability in @zalastax/nolb-om_ Package

@zalastax/nolb-om_ Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12803: Malicious code in @zalastax/nolb-om_ (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The @zalastax/nolb-om_ package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and various features. However, it has been identified to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @zalastax/nolb-om_ package. This code can lead to unauthorized access, data breaches, or other harmful actions within the application. The issue was introduced from version 0 and affects all subsequent versions. The implications of this vulnerability can be severe, potentially compromising the security and integrity of applications utilizing this package.

How To Fix

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

npm uninstall @zalastax/nolb-om_

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

If immediate updating is not feasible, consider removing the package from your project or replacing it with an alternative library that offers similar functionality without the associated risks.

Conclusion

The @zalastax/nolb-om_ package contains a critical vulnerability due to malicious code. It is essential to take immediate action by updating the package or implementing workarounds to mitigate risks. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

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

Share this vulnerability

FAQ

The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromise.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Consider removing the package or replacing it with a safer alternative until you can update.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities using just your package-lock.json.

Ignoring this vulnerability can lead to severe security breaches, data loss, and damage to your application's reputation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall @zalastax/nolb-om_

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