Malicious Code Detected in @zalastax/nolb-react-p Package
Summary
MAL-2025-13706: Malicious code in @zalastax/nolb-react-p (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-react-p package is an npm library designed for React applications, providing various functionalities to enhance user interfaces. However, it has been identified as containing malicious code, which poses significant security risks to applications that utilize it. This vulnerability can compromise the integrity of applications and potentially expose sensitive data.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-react-p package originates from the inclusion of malicious code within its distribution. This code can execute harmful actions when the package is used in applications, leading to unauthorized access, data breaches, or other malicious activities. The presence of this vulnerability is particularly concerning for developers who rely on this package for their projects, as it undermines the security of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-pIf 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 replace the @zalastax/nolb-react-p package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and consider using well-known and trusted packages.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-p package highlights the importance of vigilance in managing open-source dependencies. Developers should take immediate action to remove the affected package and consider alternatives to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-react-p →
FAQ
The malicious code can execute harmful actions that may compromise application security, such as unauthorized data access.
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.
Remove the @zalastax/nolb-react-p package immediately and consider using an alternative library.
Currently, there is no patched version available. It is crucial to monitor the package repository for any updates.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only use well-maintained packages from trusted sources.
