Malicious Code Detected in @zalastax/nolb-parse4 Package
Summary
MAL-2025-12978: Malicious code in @zalastax/nolb-parse4 (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-parse4 package is an npm library designed for parsing 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 security risks to users who have integrated it into their projects.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-parse4 package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code may 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 to protect their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-parse4If 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 using alternative packages that provide similar functionality without the security risks associated with @zalastax/nolb-parse4. Always ensure to review the security status of any new packages before integration.
Conclusion
The discovery of malicious code in the @zalastax/nolb-parse4 package highlights the importance of vigilance when using open-source libraries. Users are urged to take immediate action to remove the affected package and consider alternatives to safeguard their applications.
See every vulnerability recorded for @zalastax/nolb-parse4 →
FAQ
The malicious code can potentially allow unauthorized access to the system, leading to data breaches or other harmful actions.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.
It is recommended to remove the package immediately and look for alternative solutions until a patched version is released.
Regularly monitor your dependencies using tools like Vulert to stay informed about vulnerabilities in your open-source packages.
Detailed information can be found in the vulnerability report on GitHub and through security advisories related to npm packages.
