Malicious Code Detected in @zalastax/nolb-promisel Package
Summary
MAL-2025-13379: Malicious code in @zalastax/nolb-promisel (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-promisel package is an npm library designed for handling promises in a more manageable way. It aims to simplify asynchronous programming by providing a set of utilities that enhance promise handling. However, it has been found to contain malicious code, which poses a significant risk to users and their applications.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-promisel package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious code was introduced in version 0 and affects all subsequent versions, making it critical 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-promisel
If 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, users can avoid using the @zalastax/nolb-promisel package altogether and look for alternative libraries that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-promisel package highlights the importance of vigilance when using open-source libraries. Users are urged to take immediate action to remove the affected package and explore safer alternatives. Regular monitoring and updates are essential to maintaining application security.
See every vulnerability recorded for @zalastax/nolb-promisel →
FAQ
The malicious code can potentially allow unauthorized access to user data and compromise application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Immediately remove the package from your project and consider using alternative libraries that do not have known vulnerabilities.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.
Using malicious packages can lead to data breaches, unauthorized access, and potential damage to your application's integrity and reputation.