Malicious Code Detected in @zalastax/nolb-nodebb-p Package

@zalastax/nolb-nodebb-p Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12717: Malicious code in @zalastax/nolb-nodebb-p (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-nodebb-p package is an npm library designed for integration with NodeBB, a popular forum software. It provides various functionalities to enhance the NodeBB experience. However, this package has been found to contain malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-nodebb-p package. This code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. Users of this package are at risk of exploitation if they do not take immediate action to mitigate the threat.

How To Fix

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

npm uninstall @zalastax/nolb-nodebb-p

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 avoid using the @zalastax/nolb-nodebb-p package until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the @zalastax/nolb-nodebb-p package highlights the importance of vigilance in managing open-source dependencies. Users must take proactive steps to secure their applications by removing the affected package and monitoring for updates.

See every vulnerability recorded for @zalastax/nolb-nodebb-p →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

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

Immediately uninstall the package using npm uninstall @zalastax/nolb-nodebb-p and monitor for updates regarding a secure version.

It is highly discouraged to continue using the application with this vulnerability, as it poses significant security risks.

How To Fix

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

npm uninstall @zalastax/nolb-nodebb-p

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