Malicious Code Detected in @zalastax/nolb-arrayo Package

@zalastax/nolb-arrayo Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-10700: Malicious code in @zalastax/nolb-arrayo (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-arrayo package is an npm library designed for array manipulation and handling. It provides various utilities for developers to manage arrays efficiently. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize this package.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @zalastax/nolb-arrayo package. This code can potentially compromise the security of applications that depend on it, 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-arrayo

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-arrayo package from your project until a safe version is released. Use the following command to uninstall it: 'npm uninstall @zalastax/nolb-arrayo'.

Conclusion

The discovery of malicious code in the @zalastax/nolb-arrayo package poses a serious threat to developers and their applications. Immediate action is required to mitigate risks, including updating or removing the package. Staying informed and utilizing tools like Vulert can help maintain the security of your software.

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

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that use this package.

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.

Currently, there is no specific patched version available. Users are advised to uninstall the package until a safe version is released.

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

Utilize tools like Vulert to monitor your package-lock.json for vulnerabilities and receive alerts in real-time.

How To Fix

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

npm uninstall @zalastax/nolb-arrayo

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