Malicious Code Detected in @zalastax/nolb-react-sr Package
Summary
MAL-2025-13773: Malicious code in @zalastax/nolb-react-sr (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-sr package is an npm library designed for React applications, providing specific functionalities that enhance user experience. However, it has been identified to contain malicious code, posing significant security risks to applications that utilize it. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-react-sr package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially allow attackers to execute harmful actions, such as data theft or unauthorized access to sensitive information. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-srIf 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 avoid using the @zalastax/nolb-react-sr package until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-sr package highlights the importance of vigilance in managing open-source dependencies. Developers should take proactive measures to remove the affected package and monitor for updates. Utilizing tools like Vulert can aid in maintaining secure software environments.
See every vulnerability recorded for @zalastax/nolb-react-sr →
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 any signup.
Remove the package immediately and look for alternative solutions. Monitor for any updates or patches that may address the vulnerability.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.
Yes, if you are using the affected package in production, it could expose your application to security risks. Immediate action is recommended.
