---
title: "The Attack Path: mobile app teardowns | Ditto"
description: "Three teardowns of mobile apps that passed their security checks: the attack path, what each control missed, and a release checklist mapped to OWASP MASVS."
---

[![Ditto](https://discover.ditto.id/hubfs/ditto-lp-2026/protect-assessment/Ditto-Strapline-Orange.svg)](https://www.ditto.id/)

[Get the teardowns](https://discover.ditto.id/attack-path-developer-lp_general#form)

Attack path · Technical teardowns

# What protected releases still give away

Download the teardowns of banking, fintech and insurance apps that passed their security checks.

See what an attacker could reach, what the team relied on, and how to check your own build.

- The attack path, step by step
- What each control missed, and why
- A release checklist mapped to OWASP MASVS

[Get the teardowns](https://discover.ditto.id/attack-path-developer-lp_general#form)

![attack-path-hero-transparent](https://discover.ditto.id/hs-fs/hubfs/ditto-lp-2026/App%20teardown/attack-path-hero-transparent.png?width=2200&height=2000&name=attack-path-hero-transparent.png)

Inside the teardown

## Protected on paper isn't protected

Each teardown follows an app built from real Ditto Protect assessments. The apps had obfuscation, pinning, root detection and a pen test. These findings got through anyway.

### What you'll get

- The findings per app, in the order an attacker would find them
- What the team relied on, and the exact gap it left
- Key things to check in your own build
- Fixes at source, plus what runtime protection can and can't close
- A release checklist mapped to OWASP MASVS v2

### Get the Attack Path teardown report

Free, for mobile developers and security engineers.

Sector teardowns

## See findings from an app that looks like yours

![Attack Path teardown cover: Larkspur Pay, payments](https://discover.ditto.id/hubfs/ditto-lp-2026/App%20teardown/attack-path-payments-technical.png)

### Payments · Larkspur Pay

What attackers could find when a fintech thought they were protected.

![Attack Path teardown cover: Northwind Banking, retail banking](https://discover.ditto.id/hubfs/ditto-lp-2026/App%20teardown/attack-path-retail-banking-technical.png)

### Retail banking · Northwind Banking

What a banking app tells an attacker before they've logged in.

![Attack Path teardown cover: Ashgrove Insure, insurance](https://discover.ditto.id/hubfs/ditto-lp-2026/App%20teardown/attack-path-insurance-technical.png)

### Insurance · Ashgrove Insure

What an insurance app gives away between the claim and the payout.

How the teardowns were made

## Built from real assessments, not a lab exercise

Each teardown draws on Ditto Protect assessment analytics and is reviewed by our mobile security team. We combined what we see across real finance and insurance apps into one composite app per sector, so the findings stay true to life without exposing any customer.

- ### Grounded in Ditto Protect analytics
  
  The findings come from what Ditto Protect assessments surface in release builds: what's readable in the package, what the app accepts on the network, and how it behaves when someone changes it.
- ### Reviewed by our security experts
  
  Our team reviewed every finding, separated real exposure from noise, and explained each one in terms a developer can act on.
- ### Told the way an attacker works
  
  Findings follow the order someone would find them, from reading the package to going after the session, so you can see how one gap opens the next.

Why it's useful

## Written to be used on your next release

1. 1
   
   ### What an attacker could do
   
   Each finding opens with the real-world consequence, so you can judge quickly how much it matters for your app.
2. 2
   
   ### What the team relied on
   
   The control that was in place, and exactly where it stopped working.
3. 3
   
   ### What to check in your build
   
   Practical checks your developers can run before release, with or without Ditto Protect.
4. 4
   
   ### How to fix it at source
   
   Fixes in code and configuration, plus an honest view of what runtime protection can and can't close.

FAQ

## About the teardowns

Who is it for?

Mobile developers, AppSec and security engineers shipping finance or insurance apps.

Are these real apps?

No. Each is a composite of real assessments, so no customer is exposed. The findings are illustrative of what we see.

Do I need Ditto Protect to use it?

No. Every check and fix works on its own.

Is there a version for leadership?

Yes. Each teardown has a companion leadership briefing.

Free teardowns

## Get the teardown reports

Three teardowns across banking, insurance and fintech, with a release checklist mapped to MASVS.

[Get the teardowns](https://discover.ditto.id/attack-path-developer-lp_general#form)

Built on trusted security and privacy standards.

![ISO 27001](https://www.ditto.id/wp-content/uploads/2026/06/A_LIGN_badge_ISO_27001-1.png) ![SOC 2](https://www.ditto.id/wp-content/uploads/2026/06/A-LIGN_badge_SOC-2-1.png) ![GDPR](https://www.ditto.id/wp-content/uploads/2026/07/Vanta_Compliance_GDPR.png)

![Ditto](https://discover.ditto.id/hubfs/ditto-lp-2026/protect-assessment/Footer-Logo.svg)

[Privacy Policy](https://www.ditto.id/privacy-policy/)[Terms of Service](https://www.ditto.id/terms/)

© 2026 Ditto.ID Ltd · Company registration 16781449 · 186 Shoreditch High Street, London, England, E1 6HU