Malicious Code Detected in @zalastax/nolb-_stdlib_n Package
Summary
MAL-2025-10450: Malicious code in @zalastax/nolb-_stdlib_n (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @zalastax/nolb-_stdlib_n package is an npm library designed for specific utility functions within JavaScript applications. It is utilized by developers for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that depend on it.
Vulnerability Detail
The vulnerability in the @zalastax/nolb-_stdlib_n package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can 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 take immediate action to mitigate the risks associated with this vulnerability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @zalastax/nolb-_stdlib_nIf 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, you can avoid using the @zalastax/nolb-_stdlib_n package in your project until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the @zalastax/nolb-_stdlib_n package highlights the importance of vigilance in managing dependencies. Users are urged to take immediate action to remove the package and monitor their applications for any potential security issues.
See every vulnerability recorded for @zalastax/nolb-_stdlib_n →
FAQ
The malicious code can lead to unauthorized access and potential data breaches in applications that utilize this package.
You can use Vulert, which monitors open-source vulnerabilities in real-time. By simply 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 and look for alternative libraries that offer similar functionality.
Immediately uninstall the package and review your application for any signs of compromise. Consider conducting a security audit.
Detailed information can be found on the GitHub repository of the malicious package, as well as through security advisories related to npm packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
