Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Android Overlay
Cyber Security

Android Overlay

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

An Android overlay is a view that appears above another app’s screen. Legitimate overlays can improve usability, but malicious overlays can hide permissions, mimic trusted interfaces, and capture sensitive input. Security teams care about overlays because they can turn a normal user interaction into a phishing or privilege escalation path.

What Android overlays are used for

Android overlays are screen elements that sit above another app’s interface. In benign cases they improve usability, for example by giving quick controls or assisting accessibility workflows. In security terms, the important point is that an overlay can visually interpose itself between the user and the underlying app, which gives it leverage over what the user sees and where they tap.

That leverage matters because the overlay is not just decoration, it can become part of the trust boundary around a sensitive action. If the underlying app is a banking app, a login screen, or a permission prompt, the overlay can reshape the user’s perception of the transaction and create room for deception.

Why malicious overlays are dangerous

Malicious overlays are dangerous because they can impersonate trusted UI, obscure warning text, and make a legitimate screen look like something else. The attack often works by waiting for the user to open a high-value app, then drawing a convincing layer above it that captures credentials, payment details, or approval clicks.

This is why overlay abuse is frequently paired with phishing and credential theft. The user believes they are interacting with the real app, but the overlay can divert input, hide context, or prompt the user to reveal sensitive information into an attacker-controlled flow.

Android banking malware has repeatedly used this pattern to steal credentials, intercept one-time codes, and push fraudulent authorisation steps. NHIMG’s Android Banking Trojans Guide shows how overlays combine with accessibility abuse and on-device fraud patterns.

How overlay attacks turn interaction into compromise

An overlay attack usually succeeds by abusing timing and trust. The malicious app stays in the background until a target app or prompt appears, then it draws a fake layer that looks close enough to the real thing to influence the user’s next action. If the user approves a permission, enters a password, or confirms a transfer, the attacker gains the outcome of that action rather than merely the screen space.

In practice, the overlay can act as a bridge between social engineering and technical compromise. It may prompt the user to re-enter credentials, conceal a system prompt, or create the illusion that an update, reauthentication, or security check is required. That is why overlays are especially effective against workflows that depend on visual confirmation and fast user decisions.

How defenders reduce exposure and verify compromise

Defenders should treat overlays as a mobile anti-phishing and anti-fraud issue, not only a usability feature. The usual defensive questions are whether risky apps are installed, whether the device permits overlay drawing in contexts that matter, and whether suspicious UI behaviour appears during login, payment, or consent flows.

Post-incident review should look for evidence that a user saw one screen while the app actually processed another. That includes unexpected permission grants, abnormal authentication events, unexplained payment approvals, repeated reauthentication prompts, or signs that the user interacted with a screen that did not match the underlying app state.

Platform guidance on hardened Android configurations is useful here because the overlay risk is tightly connected to broader device trust and app-control decisions. For general control context, NIST SP 800-53 Rev 5 Security and Privacy Controls, NIST Cybersecurity Framework 2.0, and MITRE ATT&CK Enterprise Matrix provide broader control and threat-mapping reference points for detection and response.

Risk and Threat Considerations

Overlay abuse is risky because it converts ordinary screen interaction into a deception channel. The user thinks they are approving one thing, but the attacker can present a different meaning, which makes overlays useful for phishing, consent abuse, and fraudulent authorisation on mobile devices.

Failure mechanism: A malicious app gains permission or runtime ability to draw above other apps, then times a convincing fake layer over a real login, payment, or permission screen so the user supplies input or approval to the attacker’s flow.

Impact: Credentials, tokens, payment approvals, and sensitive user decisions can be captured or redirected, leading to account takeover, fraudulent transactions, or escalation from app access to broader device compromise.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-5 — Account ManagementOverlay abuse often targets user approvals and account access flows.
Recommendation — Restrict risky app capabilities and review mobile accounts that interact with sensitive workflows.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication and Access ControlOverlays can subvert authentication and authorization decisions on mobile devices.
Recommendation — Harden sensitive mobile flows so approvals and reauthentication resist deceptive UI layering.
MITRE ATT&CKT1185 — Browser Session CookieOverlay phishing often aims to steal active session material or approve attacker-controlled actions.
Recommendation — Map overlay-driven theft and session abuse paths to ATT&CK techniques in detection engineering.

Practitioner Guidance

What to watch for: Investigators should treat overlay-related reports as a UI trust problem, not only a malware indicator. A strong clue is a mismatch between what the user recalls seeing and what the backend logs show, especially around permissions, authentication prompts, and financial or administrative actions.

Governance implication: Mobile security teams should decide which app classes are allowed to draw overlays, which device integrity checks must pass before sensitive workflows proceed, and which user journeys should be hardened against deceptive screen layering.

Practitioner takeaway: The safest design is the one that assumes the screen can be lied to, then validates the action with signals that do not depend on the overlayed UI.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org