Banking Report 2025: Security at the Core of Mobile Finance(opens in a new tab)
Findings from more than 500 mobile banking apps: which protections are in place and where the gaps are. Includes a PDF report.
Research
Mobile and banking security studies, vulnerabilities we disclosed, what our AI agents found, and the open-source tools we maintain. Every item links to the full write-up or code, so your team can check the details.
Items shown: 26
Studies of mobile banking apps, vulnerabilities we found and reported, and threat research on banking malware.
Banking report series
Two editions of our study of mobile banking apps. Read them together to see how protections and common weaknesses evolve.
Findings from more than 500 mobile banking apps: which protections are in place and where the gaps are. Includes a PDF report.
The earlier edition, on banking apps in North America, for a point of comparison.
Five CVEs in ZIP libraries used by iOS and Flutter apps: a dependency risk your own apps can inherit.
A chain from Signal down to the Android SDK. Signal acknowledged the report in 3 hours and fixed it; no CVE was assigned.
Five production banking apps tested against four commercial shielding products, showing where detection works but enforcement does not.
Static analysis of a multi-stage Android banking malware platform, the kind of threat your customers' phones face.
Custom URL scheme hijacking that leads to account takeover, a pattern that applies to mobile banking login flows.
From remote compromise to data leaks in an app with more than 100 million installs.
Vulnerabilities found by our AI engine during agentic penetration testing, in mobile apps first, then in the APIs behind them.
Our AI engine found a WebView JavaScript bridge in an Android app that could be reached through deep links.
The AI engine found vulnerability classes it was not told to look for, including a WebView Safe Browsing bypass.
How the AI engine found an Android intent redirection and proved it with a working proof of concept.
A broken access control in the GraphQL subscriptions of a backend API: the servers behind your mobile app.
An account takeover through a password reset flow still exposed on an older API version.
Practical write-ups for mobile security practitioners: obfuscation, instrumentation, reverse engineering and pinning.
How to recover readable code from obfuscated Android apps with signature matching and LLM rewrites.
Hands-on dynamic instrumentation of Swift code in iOS apps.
How to reverse engineer and assess apps built with Flutter.
A universal SSL pinning bypass with LLDB, from theory to a working proof of concept.
Security testing of iOS apps on non-jailbroken devices, from a Linux workstation.
A detection approach for dependency confusion that uses source map files.
Deliberately vulnerable apps and benchmarks you can run to evaluate any mobile security tool, including ours.
93 vulnerable mobile apps based on real CVEs and bug bounty findings, open for anyone to test tools against.
Repositories
Deliberately vulnerable apps that anyone can run as test targets.
Deliberately vulnerable Flutter apps for learning and for testing tools.
Tools we build and maintain in the open.
Our open-source security scanning orchestrator: more than 15,000 PyPI downloads a month and 113 releases in the last 12 months.
One command to detect known exploited vulnerabilities, using CISA KEV, Tsunami and Asteroid.
The remote vulnerability detection agent behind KEV.
Scan every release from GitHub Actions, Azure DevOps or GitLab CI.
Plus more than 30 open-source agents, including Nmap, ZAP, Nuclei, Tsunami, OpenVAS, Semgrep and TruffleHog.Browse the agents (opens in a new tab)
Ostorlab's agentic penetration testing builds on this research to test every release of your mobile app.