Malicious Code Detected in @zalastax/nolb-react-pn Package
Summary
MAL-2025-13720: Malicious code in @zalastax/nolb-react-pn (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-pn package is a library designed for React applications, providing various functionalities for building user interfaces. It is part of the npm ecosystem, which is widely used for managing JavaScript packages. However, this package has been identified to contain malicious code, posing a significant risk to applications that depend on it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-pn package. This code can potentially compromise the security of applications using 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-pnIf 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 may consider removing the @zalastax/nolb-react-pn package from your project until a secure version is released. You can do this by running the command: npm uninstall @zalastax/nolb-react-pn.
Conclusion
The discovery of malicious code in the @zalastax/nolb-react-pn package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to secure their applications by updating or removing the affected package.
See every vulnerability recorded for @zalastax/nolb-react-pn →
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. Simply upload your package-lock.json file to check for vulnerabilities.
Yes, you can temporarily remove the package from your project or replace it with an alternative library until a secure version is available.
It is crucial to remove the package immediately and monitor your application for any unusual activity. Consider updating to a secure version as soon as it is released.
Detailed information can be found in the vulnerability report on GitHub or through security advisories related to the npm ecosystem.
