Malicious Code Detected in @zalastax/nolb-node-rec Package

@zalastax/nolb-node-rec Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12646: Malicious code in @zalastax/nolb-node-rec (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-node-rec package is an npm library designed for recording and managing network operations in Node.js applications. It offers developers a way to capture and analyze network requests and responses, making it easier to debug and optimize applications. However, this package has been found to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-node-rec package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue originates from the package's version 0 and has been identified as a significant threat to users who have integrated this package into their projects.

How To Fix

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

npm uninstall @zalastax/nolb-node-rec

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 replace the functionality provided by the @zalastax/nolb-node-rec package with alternative libraries that offer similar features without the associated risks. Consider using well-established packages that have a good reputation in the community.

Conclusion

The discovery of malicious code in the @zalastax/nolb-node-rec package highlights the importance of vigilance when using open-source libraries. Users are advised to take immediate action to remove the affected package and consider alternative solutions to safeguard their applications.

See every vulnerability recorded for @zalastax/nolb-node-rec →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise the integrity of applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts. You can also check your application using the Vulert playground without any signup.

Immediately remove the @zalastax/nolb-node-rec package from your project and look for alternative libraries to replace its functionality.

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

You can find detailed information about this vulnerability on the GitHub repository of the package or through security advisory platforms.

How To Fix

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

npm uninstall @zalastax/nolb-node-rec

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