Malicious Code Detected in @zalastax/nolb-nodebb-plugin-q: A Critical Vulnerability

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-12742: Malicious code in @zalastax/nolb-nodebb-plugin-q (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 package @zalastax/nolb-nodebb-plugin-q is an npm plugin designed for integration with NodeBB, a forum software. This plugin aims to enhance the functionality of NodeBB by providing additional features. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-nodebb-plugin-q package. This code can potentially compromise the security of applications using this plugin, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall @zalastax/nolb-nodebb-plugin-q

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 plugins that provide similar functionality without the associated risks. Always ensure to review the security of third-party packages before integrating them into your application.

Conclusion

The discovery of malicious code in the @zalastax/nolb-nodebb-plugin-q package highlights the importance of vigilance when using third-party plugins. It is crucial to take immediate action to mitigate risks by uninstalling the affected package and considering alternatives. Utilizing tools like Vulert can help maintain the security of your applications.

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

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately and look for alternative solutions or wait for a patched version.

Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Ignoring this vulnerability could lead to severe security breaches, including data loss, unauthorized access, and damage to your application's reputation.

How To Fix

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

npm uninstall @zalastax/nolb-nodebb-plugin-q

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