Malicious Code Detected in @zalastax/nolb-node-i Package
Summary
MAL-2025-12627: Malicious code in @zalastax/nolb-node-i (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-node-i package is an npm module designed for specific functionalities within Node.js applications. It is utilized by developers for its intended features, but it has been compromised, leading to the introduction of malicious code. This vulnerability poses a significant risk to applications that depend on this package, potentially allowing unauthorized access or manipulation of data.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-node-i package stems from the inclusion of malicious code, which was identified in version 0 and potentially affects all subsequent versions. This malicious code can lead to severe consequences, including data breaches, unauthorized access to user information, and exploitation of the host system. The origin of this vulnerability is linked to the package's maintainer, who has introduced harmful elements into the codebase, making it imperative 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-node-iIf 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 associated risks. Always ensure to review the package's security history before integrating it into your project.
Conclusion
The discovery of malicious code in the @zalastax/nolb-node-i package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability by uninstalling the affected package and considering alternatives.
See every vulnerability recorded for @zalastax/nolb-node-i →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and compromise the security of applications using this package.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Immediately uninstall the package using npm uninstall @zalastax/nolb-node-i and look for alternative solutions.
While specific exploits have not been publicly disclosed, the presence of malicious code indicates a high risk of exploitation.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
