Success storyUse casesBanking · TelecomIronSKY

Three attack scenarios: HTTPS hijacking, silent reconnaissance and staff faking their GPS

The device your customer trusts most is the one you can least control. Three real scenarios from SecIron deployments show what mobile fraud looks like on an actual device, and how each one was caught.

Mobile fraud has moved off the server and onto the device. Banking, telecom and enterprise apps now run on hardware, operating systems and networks the business does not own, and independent threat research from 2025 to 2026 shows the shift compounding rather than slowing.

271%year-on-year rise in unique mobile banking trojan packages
60%of mobile banking apps lack SSL pinning or equivalent controls
1 in 20verification attempts to online financial services now estimated to be fraudulent

Three components sit behind the numbers: on-device fraud that initiates transactions from the victim’s own session, app stores that no longer act as a reliable gate, and location and identity signals that are now trivially faked. The three use cases below show each one in action.

Use case 1: HTTPS hijacking against a large bank

Attackers were intercepting customer traffic to get past the bank’s identity verification. No server breach was needed, only a compromised device, which left defences that watch the server side blind to it. SecIron saw the attacks on the device, blocked them in real time and showed the bank where they were coming from. The scale of what turned up in a single day is in the full document.

Use case 2: unknown penetration attacks against a bank

The bank had no way to see hidden weaknesses in its app, or to know that someone was already mapping them. Within a day of inspection, SecIron identified a coordinated group probing the app with attack tooling, and assessed what they were likely to try next. How the activity was traced, and what the bank did about it, is in the full document.

Use case 3: location fraud at a telco

Outsourced field staff were using location-spoofing tools to “check in” without being there, and the company was paying for work that never happened. SecIron detected the spoofing on the device, blocked it and identified the tools and devices involved. The number of people caught is in the full document.

In every case the visibility came from IronSKY: real-time detection on the device, with each event logged and reported.

Why SecIron, not a workaround

Building this in-house, or patching it with point tools, doesn’t hold. SecIron follows an Adaptive Security Architecture in which protection runs as a continuous cycle of prevent, detect, respond and predict, so the platform adapts as attackers change tactics. Three products sit behind every use case above: IronSCAN scans for vulnerabilities before release, IronWALL hardens the built app with no source changes, and IronSKY monitors and responds in real time with every detection logged.

The full document includes the threat data sources, each use case in detail and the platform comparison. Download it below.

SecIron Use Cases: Attack Scenarios shown on a tablet
Download the use cases

Get the three attack scenarios in full

Seven pages covering the threat data behind the shift to on-device fraud, each scenario as it looked on a real device, and how SecIron caught it.

  • The 2025 to 2026 threat numbers and their sources
  • HTTPS hijacking at a bank: how many attacks landed in one day, and how they were stopped
  • Reconnaissance against a bank: what was found on day one, and who was behind it
  • Location fraud at a telco: how many staff were caught, and how
  • Why point tools and in-house builds don’t hold

Tell us where to send it

Use Case Form
Thank you. Your use cases are ready.

Open the PDF now, or come back to this page any time.

Download the use cases (PDF)See how this applies to your app: request a demo or talk to our experts.

We use your details to send the use cases and relevant SecIron updates. Unsubscribe at any time. See our privacy policy.

See it on your own app

Get a clearer view of your mobile app’s security posture. Speak with a SecIron expert about assessing potential vulnerabilities, risks and areas of exposure.