Malicious Package in @impala/bmap
Summary
GHSA-c82c-8pjw-6829: Malicious Package in @impala/bmap. Affects @impala/bmap versions 1.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
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 @impala/bmap package is an npm package used for mapping and geolocation functionality. It provides a set of tools and APIs to integrate mapping features into web applications. However, version 1.0.3 of this package contained malicious code that poses a security risk to applications using it.
Vulnerability Detail
The vulnerability in version 1.0.3 of @impala/bmap involves the presence of malicious code. When executed in the browser, this code would extract sensitive information such as passwords, cvc, and card numbers from forms and send them to a remote server at https://js-metrics.com/minjs.php?pl=. This can lead to unauthorized access to user data and potential misuse of sensitive information. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.
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
In conclusion, version 1.0.3 of @impala/bmap contained malicious code that could extract sensitive information from forms in the browser. It is crucial to replace this version with a safe version and evaluate your application for any potential data compromise. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for @impala/bmap →
FAQ
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any vulnerable versions are detected.
The potential consequences of this vulnerability include unauthorized access to user data, potential misuse of sensitive information, and compromise of user privacy. It is crucial to address this vulnerability promptly to protect your application and its users.
Yes, versions before and after 1.0.3 of @impala/bmap are considered safe. It is recommended to update to a safe version to mitigate the risk of this vulnerability.
If your application is affected by this vulnerability, you should immediately replace version 1.0.3 of @impala/bmap with a safe version. Additionally, you should evaluate your application to determine if any user data was compromised and take appropriate actions to mitigate the impact.
To prevent similar vulnerabilities in the future, it is important to regularly update your dependencies to the latest secure versions. Stay informed about security advisories and vulnerability reports for the packages you use in your application. Consider using tools like Vulert (https://vulert.com) to monitor and alert you in real-time for open-source vulnerabilities in your software.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
