Secure coding technique: Let's talk about Tapjacking
Tapjacking, a combination of "tap" and "hijacking", means just that. It is an attack where the attacker hijacks the users taps and tricks him into doing something he did not intend. So how does it work and how do we prevent it?
Well start our story with screen overlays. Screen overlays or as Google calls them, windows using the type TYPE_APPLICATION_OVERLAY. These are windows that are drawn on top of other apps and usually only obscure a part of the screen. These are often used (like the example image below) when an app requests new permissions.
This is actually a cool and fun feature and more and more apps are starting to use it, think about Facebooks chat bubbles, or Google Maps navigation in a corner of your screen, like the screenshot below.
However, there are some security risks involved with these overlays. Any active screen overlay can listen for taps, how else would Facebook know that we tapped or dragged the bubble? This allows apps to spy on you and potentially steal passwords and credit card data.
One step further, and this is where the term tapjacking comes from, overlays can draw things on top of other apps tricking the user to perform different actions. The user thinks he is interacting with the overlay but in reality, his taps also perform actions in the underlying app. This way, the overlay can trick you into enabling certain permissions, or change some dangerous settings, as demonstrated in this old YouTube video.
The demonstration video above was uploaded to YouTube in 2010, so it was done on an older version of Android. But the attack is still relevant today, as vulnerabilities came to light that allows tapjacking in newer versions of Android such as Nougat and Marshmallow.
So what can you do about it? As a user, it is important to realize the consequences of these overlays and be aware of apps that use it. As of API level 23 (Android 6.0 Marshmallow), this has become a permission that has to be explicitly granted by the user. However, that leaves 50% of Androidusers still vulnerable. You can still check what apps make use of this permission in the settings under "Display over other apps".
As developers, it is up to us to make sure user actions are done with the full knowledge and consent of the user. Android provides a setting for your views that do just that, called filterTouchesWhenObscured. When it is enabled, the framework will discard touches that are received whenever the views window is obscured by another visible window. Its as simple as that, set filterTouchesWhenObscured to true, and your app is safe from tapjacking.
Good luck and see you next week!
Sometimes it is essential that an application be able to verify that an action is being performed with the full knowledge and consent of the user, such as granting a permission request, making a purchase or clicking on an advertisement. Unfortunately, a malicious application could try to spoof the user into performing these actions, unaware, by concealing the intended purpose of the view.
https://developer.android.com/reference/android/view/View.html
Sometimes it is essential that an application be able to verify that an action is being performed with the full knowledge and consent of the user
Application Security Researcher - R&D Engineer - PhD Candidate
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demo
Application Security Researcher - R&D Engineer - PhD Candidate
Tapjacking, a combination of "tap" and "hijacking", means just that. It is an attack where the attacker hijacks the users taps and tricks him into doing something he did not intend. So how does it work and how do we prevent it?
Well start our story with screen overlays. Screen overlays or as Google calls them, windows using the type TYPE_APPLICATION_OVERLAY. These are windows that are drawn on top of other apps and usually only obscure a part of the screen. These are often used (like the example image below) when an app requests new permissions.
This is actually a cool and fun feature and more and more apps are starting to use it, think about Facebooks chat bubbles, or Google Maps navigation in a corner of your screen, like the screenshot below.
However, there are some security risks involved with these overlays. Any active screen overlay can listen for taps, how else would Facebook know that we tapped or dragged the bubble? This allows apps to spy on you and potentially steal passwords and credit card data.
One step further, and this is where the term tapjacking comes from, overlays can draw things on top of other apps tricking the user to perform different actions. The user thinks he is interacting with the overlay but in reality, his taps also perform actions in the underlying app. This way, the overlay can trick you into enabling certain permissions, or change some dangerous settings, as demonstrated in this old YouTube video.
The demonstration video above was uploaded to YouTube in 2010, so it was done on an older version of Android. But the attack is still relevant today, as vulnerabilities came to light that allows tapjacking in newer versions of Android such as Nougat and Marshmallow.
So what can you do about it? As a user, it is important to realize the consequences of these overlays and be aware of apps that use it. As of API level 23 (Android 6.0 Marshmallow), this has become a permission that has to be explicitly granted by the user. However, that leaves 50% of Androidusers still vulnerable. You can still check what apps make use of this permission in the settings under "Display over other apps".
As developers, it is up to us to make sure user actions are done with the full knowledge and consent of the user. Android provides a setting for your views that do just that, called filterTouchesWhenObscured. When it is enabled, the framework will discard touches that are received whenever the views window is obscured by another visible window. Its as simple as that, set filterTouchesWhenObscured to true, and your app is safe from tapjacking.
Good luck and see you next week!
Sometimes it is essential that an application be able to verify that an action is being performed with the full knowledge and consent of the user, such as granting a permission request, making a purchase or clicking on an advertisement. Unfortunately, a malicious application could try to spoof the user into performing these actions, unaware, by concealing the intended purpose of the view.
https://developer.android.com/reference/android/view/View.html
Tapjacking, a combination of "tap" and "hijacking", means just that. It is an attack where the attacker hijacks the users taps and tricks him into doing something he did not intend. So how does it work and how do we prevent it?
Well start our story with screen overlays. Screen overlays or as Google calls them, windows using the type TYPE_APPLICATION_OVERLAY. These are windows that are drawn on top of other apps and usually only obscure a part of the screen. These are often used (like the example image below) when an app requests new permissions.
This is actually a cool and fun feature and more and more apps are starting to use it, think about Facebooks chat bubbles, or Google Maps navigation in a corner of your screen, like the screenshot below.
However, there are some security risks involved with these overlays. Any active screen overlay can listen for taps, how else would Facebook know that we tapped or dragged the bubble? This allows apps to spy on you and potentially steal passwords and credit card data.
One step further, and this is where the term tapjacking comes from, overlays can draw things on top of other apps tricking the user to perform different actions. The user thinks he is interacting with the overlay but in reality, his taps also perform actions in the underlying app. This way, the overlay can trick you into enabling certain permissions, or change some dangerous settings, as demonstrated in this old YouTube video.
The demonstration video above was uploaded to YouTube in 2010, so it was done on an older version of Android. But the attack is still relevant today, as vulnerabilities came to light that allows tapjacking in newer versions of Android such as Nougat and Marshmallow.
So what can you do about it? As a user, it is important to realize the consequences of these overlays and be aware of apps that use it. As of API level 23 (Android 6.0 Marshmallow), this has become a permission that has to be explicitly granted by the user. However, that leaves 50% of Androidusers still vulnerable. You can still check what apps make use of this permission in the settings under "Display over other apps".
As developers, it is up to us to make sure user actions are done with the full knowledge and consent of the user. Android provides a setting for your views that do just that, called filterTouchesWhenObscured. When it is enabled, the framework will discard touches that are received whenever the views window is obscured by another visible window. Its as simple as that, set filterTouchesWhenObscured to true, and your app is safe from tapjacking.
Good luck and see you next week!
Sometimes it is essential that an application be able to verify that an action is being performed with the full knowledge and consent of the user, such as granting a permission request, making a purchase or clicking on an advertisement. Unfortunately, a malicious application could try to spoof the user into performing these actions, unaware, by concealing the intended purpose of the view.
https://developer.android.com/reference/android/view/View.html
Click on the link below and download the PDF of this resource.
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
View reportBook a demo
Application Security Researcher - R&D Engineer - PhD Candidate
Tapjacking, a combination of "tap" and "hijacking", means just that. It is an attack where the attacker hijacks the users taps and tricks him into doing something he did not intend. So how does it work and how do we prevent it?
Well start our story with screen overlays. Screen overlays or as Google calls them, windows using the type TYPE_APPLICATION_OVERLAY. These are windows that are drawn on top of other apps and usually only obscure a part of the screen. These are often used (like the example image below) when an app requests new permissions.
This is actually a cool and fun feature and more and more apps are starting to use it, think about Facebooks chat bubbles, or Google Maps navigation in a corner of your screen, like the screenshot below.
However, there are some security risks involved with these overlays. Any active screen overlay can listen for taps, how else would Facebook know that we tapped or dragged the bubble? This allows apps to spy on you and potentially steal passwords and credit card data.
One step further, and this is where the term tapjacking comes from, overlays can draw things on top of other apps tricking the user to perform different actions. The user thinks he is interacting with the overlay but in reality, his taps also perform actions in the underlying app. This way, the overlay can trick you into enabling certain permissions, or change some dangerous settings, as demonstrated in this old YouTube video.
The demonstration video above was uploaded to YouTube in 2010, so it was done on an older version of Android. But the attack is still relevant today, as vulnerabilities came to light that allows tapjacking in newer versions of Android such as Nougat and Marshmallow.
So what can you do about it? As a user, it is important to realize the consequences of these overlays and be aware of apps that use it. As of API level 23 (Android 6.0 Marshmallow), this has become a permission that has to be explicitly granted by the user. However, that leaves 50% of Androidusers still vulnerable. You can still check what apps make use of this permission in the settings under "Display over other apps".
As developers, it is up to us to make sure user actions are done with the full knowledge and consent of the user. Android provides a setting for your views that do just that, called filterTouchesWhenObscured. When it is enabled, the framework will discard touches that are received whenever the views window is obscured by another visible window. Its as simple as that, set filterTouchesWhenObscured to true, and your app is safe from tapjacking.
Good luck and see you next week!
Sometimes it is essential that an application be able to verify that an action is being performed with the full knowledge and consent of the user, such as granting a permission request, making a purchase or clicking on an advertisement. Unfortunately, a malicious application could try to spoof the user into performing these actions, unaware, by concealing the intended purpose of the view.
https://developer.android.com/reference/android/view/View.html
Table of contents
Application Security Researcher - R&D Engineer - PhD Candidate
Secure Code Warrior is here for your organization to help you secure code across the entire software development lifecycle and create a culture in which cybersecurity is top of mind. Whether you’re an AppSec Manager, Developer, CISO, or anyone involved in security, we can help your organization reduce risks associated with insecure code.
Book a demoDownloadResources to get you started
Trust Agent:AI - Secure and scale AI-Drive development
AI is writing code. Who’s governing it? With up to 50% of AI-generated code containing security weaknesses, managing AI risk is critical. Discover how SCW's Trust Agent: AI provides the real-time visibility, proactive governance, and targeted upskilling needed to scale AI-driven development securely.
The Power of OpenText Application Security + Secure Code Warrior
OpenText Application Security and Secure Code Warrior combine vulnerability detection with AI Software Governance and developer capability. Together, they help organizations reduce risk, strengthen secure coding practices, and confidently adopt AI-driven development.
Secure Code Warrior corporate overview
Secure Code Warrior is an AI Software Governance platform designed to enable organizations to safely adopt AI-driven development by bridging the gap between development velocity and enterprise security. The platform addresses the "Visibility Gap," where security teams often lack insights into shadow AI coding tools and the origins of production code.
Secure code training topics & content
Our industry-leading content is always evolving to fit the ever changing software development landscape with your role in mind. Topics covering everything from AI to XQuery Injection, offered for a variety of roles from Architects and Engineers to Product Managers and QA. Get a sneak peek of what our content catalog has to offer by topic and role.
Resources to get you started
Observe and Secure the ADLC: A Four-Point Framework for CISOs and Development Teams Using AI
While development teams look to make the most of GenAI’s undeniable benefits, we’d like to propose a four-point foundational framework that will allow security leaders to deploy AI coding tools and agents with a higher, more relevant standard of security best practices. It details exactly what enterprises can do to ensure safe, secure code development right now, and as agentic AI becomes an even bigger factor in the future.
