Malicious Code Detected in @zalastax/nolb-async-e Package

@zalastax/nolb-async-e Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-10716: Malicious code in @zalastax/nolb-async-e (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @zalastax/nolb-async-e package is a Node.js library designed for asynchronous operations in non-blocking environments. It is commonly used in web applications to enhance performance by allowing multiple operations to run concurrently without waiting for each to complete. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-async-e package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and has been flagged as a serious threat by security experts.

How To Fix

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

npm uninstall @zalastax/nolb-async-e

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 using alternative packages that provide similar functionality without the associated risks. Review your application's dependencies and replace @zalastax/nolb-async-e with a trusted library that meets your requirements.

Conclusion

The @zalastax/nolb-async-e package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Immediate action is required to mitigate potential threats. Regular monitoring and updates of dependencies are crucial for maintaining application security.

See every vulnerability recorded for @zalastax/nolb-async-e →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or enable harmful actions within the application.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your package-lock.json file to see if it includes @zalastax/nolb-async-e.

Currently, there is no patched version available. It is advised to remove the package until a secure version is released.

If immediate removal is not possible, consider implementing strict access controls and monitoring for unusual activity in your application.

Utilize tools like Vulert to receive real-time alerts on vulnerabilities in your open-source packages without needing to install additional software.

How To Fix

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

npm uninstall @zalastax/nolb-async-e

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