Malicious Code Detected in @zalastax/nolb-parse5 Package
Summary
MAL-2025-12979: Malicious code in @zalastax/nolb-parse5 (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-parse5 package is a JavaScript library used for parsing HTML and XML documents. It is designed to facilitate the manipulation and traversal of document structures in web applications. However, this package has been found to contain malicious code, posing a significant security risk to users and applications that rely on it.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the @zalastax/nolb-parse5 package. This code can potentially compromise the security of applications that utilize this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified in version 0 and has been classified as a serious threat due to its potential impact on user data and application integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-parse5If 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 can remove the @zalastax/nolb-parse5 package from your project until a secure version is released. You can do this by running the following command: npm uninstall @zalastax/nolb-parse5. Consider using alternative libraries that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-parse5 package highlights the importance of maintaining vigilance regarding open-source dependencies. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor vulnerabilities effectively.
See every vulnerability recorded for @zalastax/nolb-parse5 →
FAQ
The malicious code is designed to exploit vulnerabilities in applications that use the package, potentially leading to unauthorized access or data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can identify if your application is affected.
Yes, Vulert allows you to monitor vulnerabilities using just your package-lock.json file, making it easy to stay informed about potential risks.
If immediate updates are not possible, consider removing the package as a temporary measure and look for alternative libraries that fulfill similar needs.
Detailed information about the vulnerability can be found on the GitHub repository of the malicious package, as well as through security advisories related to npm packages.
