GUI Overlay Opacity Checks to Block Interaction Hijacking

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

User interaction hijacking attacks occur when malicious software exploits overlapping user interface components to trick users into unintended actions by obstructing the view of the actual target component, making it difficult to detect and prevent without affecting normal device functionality.

Innovation Solution

A computing device determines the cumulative opacity of multiple overlapping user interface components to block user interactions when the combined opacity exceeds a threshold, ensuring the target component is sufficiently visible to the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple UI components are overlaid to create visual effects or pass-through functionality, then the UI flexibility and functionality are improved, but the system becomes vulnerable to user interaction hijacking attacks

Engineering Contradiction:
ImproveUI flexibilityVSAvoidinteraction hijacking vulnerability
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary detection of overlaying UI components and calculates their cumulative opacity before allowing user interactions to reach underlying components. This preemptive check prevents hijacking attacks by blocking interactions when the cumulative opacity exceeds the threshold, while still allowing legitimate overlay functionality to operate normally when transparency requirements are met.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If the system blocks user interactions when cumulative opacity exceeds threshold, then security against hijacking attacks is improved, but normal overlay functionality may be affected

Engineering Contradiction:
ImprovesecurityVSAvoidoverlay functionality
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system applies the opacity threshold check locally to specific UI components and their overlay relationships, rather than globally blocking all interactions. This allows legitimate overlay functionality to continue operating in regions where the cumulative opacity is within acceptable thresholds, while only blocking interactions in regions where hijacking is detected, thus maintaining ease of operation for normal functionality.

Inventive Principle:
Principle #3Local quality

3Difficulty of detecting and measuring

If the system monitors cumulative opacity of overlaying UI components, then detection of hijacking attacks is improved, but system complexity increases

Engineering Contradiction:
Improvehijacking detectionVSAvoidsystem complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer (the opacity calculation and comparison mechanism) that sits between the UI component stack and the interaction handling logic. This intermediary automatically calculates cumulative opacity for overlaying components and compares it against the threshold, making hijacking detection transparent and integrated into the existing UI framework without requiring complex external monitoring systems.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12499223B2Preventing user interaction hijacking attacks by blocking interactions with obscured components
Publication Date: 2025.12.16 GOOGLE LLC
  • US12499223B2 patent drawing
  • US12499223B2 patent drawing
  • US12499223B2 patent drawing

AI summary

A method includes detecting a user interaction with a particular region of a graphical user interface (GUI), and determining that the user interaction will be consumed by a particular user interface (UI) component that is overlaid by a plurality of UI components configured to allow the user interaction to pass through to the particular UI component. The method also includes, based on determining that the user interaction will be consumed by the particular UI component, determining a cumulative opacity of the plurality of UI components at the particular region of the GUI. The method further includes determining that the cumulative opacity exceeds a threshold opacity and, based on determining that the cumulative opacity exceeds the threshold opacity, blocking the particular UI component from consuming the user interaction.