maibank Security & Privacy Scorecard
Android
In-app behavior is tracked by Firebase, Amplitude, and Adjust, sharing usage patterns with multiple analytics and attribution companies. Network protection for banking sessions does not meet the expected standard, meaning data may travel with less protection than expected on public or unsecured connections. Account data handling has areas where sensitive information may not be fully protected from improper storage or access.
Best for
Everyday banking with standard analytics tradeoffs
Avoid if
You bank on public or untrusted Wi-Fi networks
Findings
- 3 critical
- 5 high
- 11 medium
- 9 low
- 0 info
0 issues identified across security and privacy analysis.
Top security issues
- WebView SSL Certificate Validation Bypass in Payment Flows
- JavaScript Interface Exposed to Untrusted Web Content (RCE Vector)
- Hardcoded Third-Party API Keys Extractable via Decompilation
Top privacy issues
- Extensive Financial Behavior Tracking by Third-Party Analytics
- Missing FLAG_SECURE on Financial Screens (Screenshot Risk)
- Child/Parent Names in Plaintext SharedPreferences (PII)
Full analysis
maibank
What This Means for You
In-app behavior is tracked by Firebase, Amplitude, and Adjust, sharing usage patterns with multiple analytics and attribution companies. Network protection for banking sessions does not meet the expected standard, meaning data may travel with less protection than expected on public or unsecured connections. Account data handling has areas where sensitive information may not be fully protected from improper storage or access.
Recommendation: Use With Caution
Best For: Everyday banking with standard analytics tradeoffs
Avoid If: Banking regularly on public or untrusted Wi-Fi networks
Key Findings
Data Security - 15 findings (3 high, 6 medium, 5 low, 1 info)
Network Security - 2 findings (1 critical, 1 high)
Code Safety - 0 findings
Privacy - 3 findings (1 high, 2 medium)
Privacy Concerns
What Data is Collected
maibank collects behavioral data including in-app interactions, session activity, and device identifiers. This data feeds into both internal analytics and the third-party services listed below.
Third-Party Data Sharing
Usage data is shared with the following services:
- Firebase Analytics - Tracks in-app behavior and session activity on Google's platform.
- Amplitude - Collects detailed behavioral data to build usage profiles tied to user activity.
- Adjust - Links in-app actions to advertising campaigns for attribution purposes.
- Google Maps - Mapping features may share location data with Google.
- Druid - Customer support platform with access to user support interaction data.
- Lokalise - Localization service used for translating app content.
- Yandex DivKit - A UI framework component from Yandex integrated into the app.
- Realm Database - A local on-device database library handling data storage.
- PairIP LicenseCheck - A licensing verification service that contacts external servers.
Understanding the Scores
| Category | Score |
|---|---|
| Security | 45/100 |
| Privacy | 55/100 |
| Data Security | 65/100 |
| Network Security | 35/100 |
| Code Safety | 40/100 |
| Data Collection | 50/100 |
| Data Sharing | 55/100 |
| User Control | 60/100 |
Positive Security Features
- No specific positive security practices were identified in this version of the app.
Areas for Improvement
- The app's network communication provides less protection than expected on untrusted connections, meaning data transmitted during active use may not be fully protected.
- Sensitive account data is handled with insufficient protections, increasing the risk that personal or financial information could be stored or accessed in ways that are not fully secure.
- The scope of third-party analytics means in-app behavior is shared with multiple external companies, with limited controls available to users.
About This Analysis
This scorecard reflects the state of the app at the time of analysis and may not reflect subsequent updates.
App Details
- App: maibank
- Package ID: md.maib.maibank
- Version: 1.0.635 (build 629)
- Scan Date: 2026-02-10
Versions & scan history
| Scan | Date | Overall score |
|---|---|---|
| #1 (current) | 50/100 |