Malicious Package in angular-bmap
Summary
GHSA-w8hg-mxvh-9h57: Malicious Package in angular-bmap. Affects angular-bmap versions 0.0.9. 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 angular-bmap package is an npm package used for integrating Baidu Maps into Angular applications. It provides components and services to easily display maps and interact with them. The package is widely used in Angular projects for incorporating map functionalities.
Vulnerability Detail
Version 0.0.9 of the angular-bmap package contained malicious code. When executed in the browser, the code would enumerate password, cvc, and cardnumber fields from forms and send the extracted values to a remote server at https://js-metrics.com/minjs.php?pl=. This malicious behavior poses a significant security risk as it can lead to the compromise of sensitive user data, including passwords and credit card information.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Conclusion
The malicious package in angular-bmap version 0.0.9 poses a critical security risk by extracting sensitive user data and sending it to a remote server. To protect your application and users, it is crucial to replace the affected package version with a safe alternative. Additionally, evaluating the potential impact on user data and taking appropriate measures to secure it is essential. For further support and assistance in vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for angular-bmap →
FAQ
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert analyzes your package-lock.json file and provides real-time monitoring and alerts for open-source vulnerabilities in your software.
The potential consequences of this vulnerability include the compromise of sensitive user data, such as passwords and credit card information. This can lead to unauthorized access, identity theft, and financial loss for affected users.
Yes, versions of angular-bmap before and after 0.0.9 are considered safe. It is recommended to update to the latest version available to ensure the absence of the malicious code.
If your application is affected by this vulnerability, you should immediately replace the angular-bmap package with a safe version and evaluate the potential impact on user data. It is advisable to notify affected users and take necessary measures to secure their accounts and information.
No, the only reliable way to mitigate the impact of this vulnerability is to replace the angular-bmap package with a safe version. Simply removing the malicious code from the package may not be sufficient, as there could be other hidden vulnerabilities or backdoors.
