Critical Malicious Code Vulnerability in @zalastax/nolb-react-sm Package
Summary
MAL-2025-13768: Malicious code in @zalastax/nolb-react-sm (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-sm package is a JavaScript library designed for use in React applications, providing various functionalities for developers. 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 originates from the presence of malicious code within the @zalastax/nolb-react-sm package. This code can compromise the integrity of applications using the package, potentially allowing attackers to execute harmful actions, steal sensitive information, or manipulate application behavior. The malicious nature of this code makes it critical for developers to address this issue promptly to safeguard their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-react-smIf 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 removing the @zalastax/nolb-react-sm package from your project until a secure version is released. You can do this by running: npm uninstall @zalastax/nolb-react-sm. This will help mitigate the risk of exposure to the malicious code while you await a fix.
Conclusion
The @zalastax/nolb-react-sm package has been identified to contain malicious code, posing a serious security threat to applications using it. Developers are urged to update or remove the package to mitigate risks. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.
See every vulnerability recorded for @zalastax/nolb-react-sm →
FAQ
The malicious code can execute unauthorized actions within applications, potentially leading to data theft or manipulation.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
As of now, there is no specific patched version available. It is crucial to monitor the package repository for updates.
If an immediate update is not possible, consider removing the package from your project as a temporary measure.
Utilizing tools like Vulert can help you stay updated on vulnerabilities in your open-source dependencies without requiring access to the code.
