Malicious Code Detected in @zalastax/nolb-parse9 Package
Summary
MAL-2025-12981: Malicious code in @zalastax/nolb-parse9 (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-parse9 package is an npm library designed for parsing and handling specific data formats. It is utilized in various applications for its efficiency and ease of integration. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-parse9 package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, 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-parse9If 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-parse9 package from your project until a secure version is released. You can do this by executing: npm uninstall @zalastax/nolb-parse9.
Conclusion
The discovery of malicious code in the @zalastax/nolb-parse9 package highlights the importance of regularly monitoring and updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability.
See every vulnerability recorded for @zalastax/nolb-parse9 →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data or execute harmful actions within your application.
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.
If an immediate update is not possible, consider removing the package from your project as a temporary measure until a secure version is available.
Yes, tools like Vulert can help you monitor your package-lock.json for vulnerabilities in real-time.
Using the compromised package can lead to data breaches, unauthorized access, and other security risks that may affect your entire application.
