Malicious Code Detected in @zalastax/nolb-json-1 Package

@zalastax/nolb-json-1 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12088: Malicious code in @zalastax/nolb-json-1 (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-json-1 package is an npm library designed for JSON manipulation and processing. It is intended to simplify the handling of JSON data structures in JavaScript applications. However, this package has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-json-1 package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of the code was discovered by Amazon Inspector, indicating that the package has been compromised since its introduction.

How To Fix

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

npm uninstall @zalastax/nolb-json-1

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 libraries for JSON manipulation that are well-reviewed and have a good security track record. Always ensure to review the package's repository for any reported vulnerabilities before integrating it into your project.

Conclusion

The @zalastax/nolb-json-1 package has been identified as containing malicious code that poses a security risk to applications. It is essential to uninstall this package and consider alternatives to safeguard your projects. Regular monitoring of dependencies is crucial for maintaining application security.

See every vulnerability recorded for @zalastax/nolb-json-1 →

Share this vulnerability

FAQ

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

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Immediately uninstall the package using npm uninstall @zalastax/nolb-json-1 and consider using alternative libraries.

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

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

How To Fix

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

npm uninstall @zalastax/nolb-json-1

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