Malicious Code Detected in @zalastax/nolb-react-id Package
Summary
MAL-2025-13687: Malicious code in @zalastax/nolb-react-id (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-id package is an npm library designed for React applications, providing unique identification functionalities for components. However, it has been found to contain malicious code, posing significant security risks to applications that utilize it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @zalastax/nolb-react-id package. This code can potentially compromise the integrity 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-idIf 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 possible, consider removing the package from your project until a secure version is released. You can do this by running: npm uninstall @zalastax/nolb-react-id.
Conclusion
The @zalastax/nolb-react-id package contains malicious code that poses significant risks to applications. Immediate action is required to update or remove the package to safeguard your application from potential threats.
See every vulnerability recorded for @zalastax/nolb-react-id →
FAQ
The malicious code can lead to unauthorized access and potential data breaches in applications using this package.
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.
Consider removing the package from your project until a secure version is available to mitigate risks.
Yes, tools like Vulert can help you monitor your dependencies in real-time using just your package-lock.json.
Ignoring this vulnerability may lead to severe security issues, including data breaches and unauthorized access to sensitive information.
