Critical Malicious Code Vulnerability in bergaa Package
Summary
MAL-2025-6403: Malicious code in bergaa (npm). Affects bergaa versions 2.0.0 – 2.0.3. 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 bergaa package is an npm library designed for various functionalities within JavaScript applications. It is widely used for its ease of integration and utility in managing tasks. However, recent findings have revealed that certain versions of bergaa contain malicious code that can compromise the security of applications utilizing this package.
Vulnerability Detail
The vulnerability identified as MAL-2025-6403 originates from malicious code embedded in versions 2.0.0 to 2.0.3 of the bergaa package. This code can potentially allow unauthorized access to sensitive data or execute harmful operations within the host application. The implications of this vulnerability are severe, as it can lead to data breaches, unauthorized control over the application, and significant reputational damage to developers and organizations using the affected package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bergaaIf 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 remove the bergaa package from their project until a secure version is confirmed. This can be achieved by executing: npm uninstall bergaa.
Conclusion
The discovery of a malicious code vulnerability in the bergaa package underscores the importance of maintaining up-to-date dependencies in software projects. Users are strongly advised to update to the latest version to mitigate risks associated with this vulnerability.
See every vulnerability recorded for bergaa →
FAQ
Versions 2.0.0 to 2.0.3 of the bergaa package are affected by the malicious code vulnerability.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
The risks include unauthorized access to sensitive data, potential data breaches, and the execution of harmful operations within your application.
Yes, updating to version 2.0.4 or later of the bergaa package will patch the vulnerability.
If immediate updates are not possible, consider removing the bergaa package from your project as a temporary measure.
