Stop Malware, Overlays & Session Takeover
App & Device Protection
The attack happens after the customer logs in. Most banks have no defence at that layer.
Banking trojans and malware targeting mobile apps grew 196% in 2024. Once a customer’s device is compromised, fraudsters can intercept credentials, overlay fake screens on top of the banking app, inject fraudulent transactions, or control the device remotely — all while the customer believes they are using their bank’s legitimate app. These attacks are invisible to authentication controls and network-level monitoring.
CBUAE has now mandated that banking sessions be suspended automatically when malware or screen-sharing is detected — a specific, enforceable requirement that most banks currently have no way to meet.
0
Banking malware growth (2024)
Banking trojans targeting mobile apps. The customer’s phone has become the primary attack surface.
0 %
Banks with runtime session protection
CBUAE mandates malware-triggered session suspension. Most banks currently have no solution for this.
Real-time
When attacks happen
Overlay and RAT attacks operate during live sessions. Detection must happen in the same timeframe — not during post-session analysis.
Use Cases Addressed
What Banks Need
Fraud no longer waits for a customer to make a mistake. Overlay attacks, remote access trojans, and repackaged app clones now target the device itself — often before a single credential is entered. Banks need real-time, on-device detection that stops these threats at the source and satisfies CBUAA’s session-suspension requirements without added friction for legitimate users.
Overlay attack prevention
Detect fake screens placed on top of the banking app before the customer enters any credentials.
Remote access tool (RAT) blocking
Malware and trojan detection
App integrity assurance
CBUAE session suspension compliance
CBUAE Notice 3057
Regulatory Alignment
Explicitly requires that banking sessions be suspended when malware or screen-sharing is detected. This is not a general security best practice — it is a specific, enforceable compliance requirement with a hard deadline that has now passed. Banks that do not have a session suspension capability are in breach.
Client Story
Proven in Production
The RASP SDK is live at UAE’s 3rd largest bank, protecting the mobile and online banking experience for 2M+ digital customers. Ektar continues to expand the SDK’s threat detection capabilities in active collaboration with this anchor client.
Get Started Today
Talk to us about app & device protection
This page explains the problem, what the regulation requires, and how Ektar solves it.