Malicious Code Detected in @zalastax/nolb-parsep Package

@zalastax/nolb-parsep Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12998: Malicious code in @zalastax/nolb-parsep (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-parsep package is an npm library designed for parsing and handling specific data formats. It is utilized in various JavaScript applications for its parsing capabilities. However, it has been found to contain malicious code that poses a security risk to users and their applications.

Vulnerability Detail

The vulnerability in the @zalastax/nolb-parsep package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code makes it imperative for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall @zalastax/nolb-parsep

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, users can remove the @zalastax/nolb-parsep package from their project until a secure version is released. This can be done using the command: npm uninstall @zalastax/nolb-parsep.

Conclusion

The discovery of malicious code in the @zalastax/nolb-parsep package highlights the importance of maintaining secure dependencies in software projects. Users must take immediate action to update or remove the affected package to protect their applications from potential threats.

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

Share this vulnerability

FAQ

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

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

Users are advised to check the package repository for any updates or patches that address this vulnerability.

As a temporary measure, consider uninstalling the package until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities without requiring access to the code or installation.

How To Fix

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

npm uninstall @zalastax/nolb-parsep

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