Android App Task Hijacking is an attack where one Android app interferes with the task or back-stack behaviour of another app. It works by abusing intent handling and activity launch modes so a malicious screen can appear in place of a legitimate one, often to steal credentials or session data.
How Android task hijacking works
Android App Task Hijacking exploits how Android groups activities into tasks and back stacks. If an app exposes launch behaviour that can be influenced, a malicious activity can be placed where the user expects the real one, creating a convincing visual handoff that can capture input, credentials, or session data without changing the underlying app.
The attack is not about breaking Android’s UI outright. It abuses ordinary platform behaviour, especially intent routing, task affinity, and activity launch modes, so the user sees a screen that feels legitimate. That makes it dangerous because trust is borrowed from the target app’s icon, history, and navigation flow rather than earned by the screen that is actually on top.
Why the back stack matters
Android’s back stack is a usability feature, but it also creates security consequences when apps do not tightly control how activities are launched and re-entered. A hijacked task can preserve the illusion of continuity, which is useful to an attacker because users often interact with the visible screen before they re-check the app identity.
That is why this class of issue is often discussed alongside intent redirection and other mobile deep link and app link security concerns. The same trust boundary problem appears when an app accepts external navigation without validating where the transition came from or where it should go next.
Task hijacking also becomes easier to exploit when the target app’s flow includes sensitive checkpoints such as sign-in, MFA, or session re-authentication. If the user is moved into a convincing overlay or substitute activity at the wrong moment, the attacker can harvest secrets that are supposed to stay inside the legitimate app context.
How organisations reduce exposure
Exposure starts with inventory and app review. Organisations need to know which mobile apps are in use, how they are distributed, and whether any expose launch paths, custom intents, or task behaviours that can be manipulated. In practice, mobile app testing should include navigation and launch-path review, not just code-level checks.
Mobile app security testing should include checks for unsafe task and activity behaviour, because a secure login screen is less useful if it can be reached through an untrusted navigation path. When deep links, redirects, or activity re-entry are part of the product design, the security team should validate those flows as explicitly as any API or authentication control.
Organisations should also treat mobile permissions and overlay-related behaviour as part of the exposure review. Even when the hijack is not caused by a permission flaw, weak app trust assumptions, permissive launch handling, and poor hardening of sensitive screens all widen the attack surface.
Detection and response after suspected hijacking
Detection is difficult because the attack often uses legitimate platform mechanics. Indicators usually come from user reports, unusual screen transitions, unexpected activity resumes, or signs that the wrong app is receiving input at a sensitive moment. Defenders should correlate those reports with mobile telemetry, app inventory, and behavioural testing rather than relying on a single alert source.
When task hijacking is suspected, the first response is to review whether credentials, tokens, or active sessions may have been exposed through the affected flow. If the attacker captured a login, password reset, or one-time code, the incident should be treated as a potential account compromise until the session state is verified and any affected access material is reissued.
The control lesson is straightforward: if an app’s navigation can be convincingly replaced, the compromise may not end when the fake screen disappears. The stolen value may already have moved into an attacker-controlled session, browser context, or follow-on phishing flow.
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 OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V6 — Authentication | Task hijacking often targets login and re-authentication screens. |
| V7 — Session Management | Hijacked tasks can expose or reuse active app sessions and tokens. | |
| Recommendation — Validate authentication flows against screen substitution and phishing-style UI abuse. Bind session handling to trusted app flows and invalidate suspect sessions after abuse. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Captured credentials or one-time secrets must be rotated after a hijack. |
| AC-6 — Least Privilege | Reducing app and user privilege limits what a spoofed mobile flow can access. | |
| Recommendation — Rotate exposed authenticators and revoke any compromised secrets immediately. Limit sensitive actions to the minimum privileges required for the mobile workflow. | ||
| MITRE ATT&CK | T1656 — Impersonation | The attack relies on a fake screen impersonating a trusted app flow. |
| Recommendation — Map spoofed mobile screens to impersonation behaviours in your detection and threat model. | ||
Practitioner Guidance
What to watch for: Task hijacking is a design and assurance problem as much as a malware problem. App teams should be especially cautious anywhere a sensitive workflow can be entered from outside the app, resumed from recents, or re-opened after backgrounding, because those are the moments when visual spoofing is most effective.
Governance implication: Mobile security owners should treat task and activity handling as part of secure app design review, not as an edge-case UI issue. If a workflow can expose credentials, session data, or authentication prompts, its launch behaviour deserves the same scrutiny as its server-side access control.
Practitioner takeaway: The safest mobile flows are the ones that do not assume the visible screen is trustworthy just because it looks familiar.
Related resources from NHI Mgmt Group
- What breaks when Android app security depends only on open-source protections?
- How should organisations respond if Android Keystore operations cause app slowdown?
- What breaks when Android app components are exposed without protection?
- What should teams do when task hijacking or intent redirection appears in testing?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org