Malicious Code Detected in @zalastax/nolb-react-px: A Critical Security Alert
Summary
MAL-2025-13729: Malicious code in @zalastax/nolb-react-px (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 package @zalastax/nolb-react-px 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, data breaches, and other malicious activities.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @zalastax/nolb-react-px package. This code can execute harmful actions without the user's consent, potentially compromising sensitive data and application integrity. The issue was introduced in version 0 and affects all subsequent versions, making it critical for developers to take immediate action to mitigate risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-px
If 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 using alternative packages that provide similar functionalities without the associated risks. Always ensure to review the security status of any package before integrating it into your project.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-px package highlights the importance of vigilance in managing open-source dependencies. Developers must take immediate action to remove the affected package and consider alternatives to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-react-px →
FAQ
The malicious code can perform unauthorized actions, potentially leading to data breaches and security vulnerabilities.
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.
Immediately uninstall the package and look for alternative solutions. If a patched version is released, update to that version as soon as possible.
While specific exploits have not been detailed, the presence of malicious code indicates a high risk for potential exploitation.
Regularly audit your dependencies, utilize tools like Vulert for monitoring, and stay informed about security advisories related to the packages you use.