Malicious Code Detected in @zalastax/nolb-random2 Package

@zalastax/nolb-random2 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13598: Malicious code in @zalastax/nolb-random2 (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 Penetration testing for web, API and mobile 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-random2 package is an npm library designed for random number generation and related functionalities. It is utilized by developers to incorporate randomness into their applications. However, this package has been flagged for containing malicious code, which poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @zalastax/nolb-random2 package. This code can potentially compromise the integrity 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-random2

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

Currently, there are no specific workarounds to mitigate the risks posed by this vulnerability other than removing the affected package from your project.

Conclusion

The @zalastax/nolb-random2 package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Immediate removal of the package is necessary, and users should stay vigilant for any updates or patches in the future.

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

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and 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 any signup.

It is recommended to remove the package immediately to prevent any potential security risks.

As of now, there is no patched version available for the @zalastax/nolb-random2 package.

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

How To Fix

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

npm uninstall @zalastax/nolb-random2

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