Malicious Code Detected in @zalastax/nolb-nodebb-w Package
Summary
MAL-2025-12755: Malicious code in @zalastax/nolb-nodebb-w (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The @zalastax/nolb-nodebb-w package is an npm module designed for integration with NodeBB, a forum software. It provides various functionalities to enhance user experience and manage forum interactions. However, this package has been found to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-nodebb-w package. This code can lead to unauthorized access, data breaches, or other harmful actions within the applications that depend on this package. The malicious nature of the code can compromise the integrity and security of the entire system, making it crucial for developers to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-nodebb-wIf 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 measure, you can remove the @zalastax/nolb-nodebb-w package from your project until a secure version is released. This can be done by executing the command: npm uninstall @zalastax/nolb-nodebb-w.
Conclusion
The discovery of malicious code in the @zalastax/nolb-nodebb-w package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers should take immediate action to mitigate risks by updating or removing the affected package.
See every vulnerability recorded for @zalastax/nolb-nodebb-w →
FAQ
The malicious code can perform unauthorized actions, potentially leading to data breaches or system compromises.
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.
If an immediate update is not possible, consider removing the package as a temporary workaround to mitigate risks.
Utilize tools like Vulert to monitor your package-lock.json for vulnerabilities and receive alerts about any issues.
Yes, you can use tools like npm-check-updates or dependabot to automate the process of checking and updating your npm packages.
