Attack Path · Mobile app security teardowns
Attack Path follows mobile apps from banking, payments and insurance that passed their security checks. They had obfuscation, certificate pinning, root detection and a pen test. Attackers could still found a way in.
Built from real assessments, not a lab exercise
Grounded in Ditto Protect analytics
The findings come from what Ditto Protect assessments surface in release builds and live sessions.
Reviewed by our security experts
Our mobile security team reviewed every finding, separated real exposure from noise, and wrote it up for the people who have to act on it.
Useful whatever you run today
Every check, fix and question works on its own. You don’t need Ditto Protect to use them.
Each sector comes in two editions that tell the same story for different readers. The technical teardown is for the people who build the app. The leadership briefing is for the people who answer for the risk.
How to use this series: choose your role below, start with the sector closest to your own app, then pass the other edition to the other side of the room.
Technical teardowns
For mobile developers, AppSec and security engineers
- The attack path, in the order an attacker would follow it
- What each control missed, and the gap it left
- Checks to run on your own build before release
- Fixes at source, plus a release checklist mapped to OWASP MASVS v2
Leadership briefings
For CISOs, CTOs, and heads of fraud and risk
- Where app exposure turns into loss for the business
- What each control was trusted to do, and where it fell short
- Questions to take into your next risk meeting
- Where live protection covers what build checks can’t
Start with the app that looks like yours
Each company is a composite built from real Ditto Protect assessments, so the findings stay true to life without exposing any customer.
Payments
Larkspur Pay
A fintech that believed it was covered, and what an attacker could still reach in its release build.
Technical teardownWhat attackers still find when you think you’re protected
Payments
Larkspur Pay
A fintech that believed it was covered, and what an attacker could still reach in its release build.
Leadership briefingWhat a “protected” released app still gives away, and what it costs the business
Retail banking
Northwind Banking
What a banking app gives an attacker before anyone has logged in, and what that exposure costs the bank.
Technical teardownWhat a banking app tells an attacker before they’ve logged in
Retail banking
Northwind Banking
What a banking app gives an attacker before anyone has logged in, and what that exposure costs the bank.
Leadership briefingWhat a “protected” banking app still gives away, and what it costs the bank
Insurance
Ashgrove Insure
Where an insurance app leaks value between the claim and the payout, and what it costs the insurer.
Technical teardownWhat an insurance app gives away between the claim and the payout
Insurance
Ashgrove Insure
Where an insurance app leaks value between the claim and the payout, and what it costs the insurer.
Leadership briefingWhat a “protected” insurance app still gives away, and what it costs the insurer
Bring both sides of the room together
The gaps in these apps sat between the people who build them and the people who answer for the risk. Read your edition, then share the other one.





