Malicious Code Detected in @zalastax/nolb-react-ii Package
Summary
MAL-2025-13692: Malicious code in @zalastax/nolb-react-ii (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-ii package is an npm library designed for building React applications with enhanced functionality. It provides various components and utilities to streamline development processes. However, this package has been found to contain malicious code, posing a significant risk to users who integrate it into their projects.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-ii package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-iiIf 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
If an immediate update is not feasible, consider removing the package from your project until a secure version is released. You can do this by running: npm uninstall @zalastax/nolb-react-ii.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-ii package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update or remove the affected package to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-react-ii →
FAQ
The malicious code can perform unauthorized actions within applications, potentially leading to data theft or system compromise.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check your application without any signup.
Consider removing the package from your project until a secure version is available to mitigate risks.
While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.
Regularly check for updates in your dependencies and utilize tools like Vulert to receive real-time alerts for vulnerabilities.
