Malicious Code Detected in @zalastax/nolb-o7 Package - MAL-2025-12789
Summary
MAL-2025-12789: Malicious code in @zalastax/nolb-o7 (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-o7 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility. However, this package has been found to harbor malicious code, posing significant security risks to applications that depend on it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-o7 package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-o7If 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 measure, consider removing the @zalastax/nolb-o7 package from your project until a secure version is released. You can do this by running: npm uninstall @zalastax/nolb-o7.
Conclusion
The discovery of malicious code in the @zalastax/nolb-o7 package highlights the importance of maintaining secure dependencies in software development. Users are urged to update or remove the affected package to mitigate potential risks.
See every vulnerability recorded for @zalastax/nolb-o7 →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data or enable other harmful actions within the 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 until a secure version is available.
While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.
Utilize tools like Vulert to monitor your package-lock.json file for vulnerabilities and receive alerts in real-time.
