Malicious Code Detected in @zalastax/nolb-pdo Package
Summary
MAL-2025-13113: Malicious code in @zalastax/nolb-pdo (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-pdo package is an npm library designed for PDO (PHP Data Objects) integration, providing developers with a streamlined way to interact with databases in PHP applications. However, this package has been identified to contain malicious code, posing a significant risk to applications utilizing it. Users of this package should be aware of its potential vulnerabilities and take immediate action to safeguard their projects.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-pdo package arises from the inclusion of malicious code that can compromise the security of applications using this library. This code could lead to unauthorized access, data breaches, or other malicious activities, making it imperative for developers to address this issue promptly. The malicious code was introduced in version 0 and affects all subsequent versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-pdoIf 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-pdo package from your project until a secure version is released. You can do this by running the following command: npm uninstall @zalastax/nolb-pdo.
Conclusion
The discovery of malicious code in the @zalastax/nolb-pdo package highlights the importance of monitoring open-source dependencies for vulnerabilities. Developers should take immediate action to update or remove the affected package to protect their applications from potential threats.
See every vulnerability recorded for @zalastax/nolb-pdo →
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 open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can alert you to any vulnerabilities, including this one.
Yes, you can temporarily remove the package from your project or replace it with a similar, secure alternative until a patched version is available.
It is crucial to immediately update the package or remove it from your application to prevent potential exploitation of the vulnerability.
Detailed information about the vulnerability can be found in the official GitHub repository and vulnerability databases.
