Malicious Code Detected in @zalastax/nolb-react-sto Package
Summary
MAL-2025-13784: Malicious code in @zalastax/nolb-react-sto (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-sto package is an npm library designed for React applications, providing various functionalities for state management and UI components. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take immediate action to safeguard their applications.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @zalastax/nolb-react-sto package. This code can lead to unauthorized access, data breaches, or other harmful actions within applications that integrate this package. The issue was introduced from version 0 onwards, making all versions susceptible to exploitation. Developers using this package should be vigilant about the risks associated with its use.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-stoIf 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 replacing the functionality provided by the @zalastax/nolb-react-sto package with alternative libraries that do not have known vulnerabilities. Ensure to review the security of any new packages before integration.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-sto package highlights the importance of maintaining vigilance in open-source software usage. Developers are urged to remove the affected package and consider alternatives to protect their applications from potential threats.
See every vulnerability recorded for @zalastax/nolb-react-sto →
FAQ
The malicious code can potentially allow unauthorized access or manipulation of application data, posing a significant security threat.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If immediate removal is not feasible, consider implementing strict access controls and monitoring to mitigate potential risks until you can replace the package.
Yes, there are several alternative libraries available for state management and UI components in React. Research and select one that meets your application's needs while ensuring it has a good security track record.
As of now, there is no patch available. It is recommended to monitor the package repository for any updates or announcements regarding a secure version.
