Incident: Phishing Scam Exploiting Google Chrome's Mobile Browser Address Bar

Published Date: 2019-04-29

Postmortem Analysis
Timeline 1. The software failure incident of the phishing scam affecting Google Chrome's mobile browser happened in April 2019 as per the article published on April 29, 2019 [83502].
System The software failure incident described in the article [83502] involved the failure of the following systems: 1. Google Chrome's mobile browser on Android 2. Address bar functionality in Google Chrome on Android
Responsible Organization 1. Hackers targeted Android mobile users using Google Chrome with a phishing scam that involved creating a fake address bar to trick users into giving up their private data [83502].
Impacted Organization 1. Android mobile users using Google Chrome were impacted by the phishing scam described in the article [83502].
Software Causes 1. The software cause of the failure incident was a phishing scam that exploited a vulnerability in Google Chrome's mobile browser, specifically targeting Android users [83502].
Non-software Causes 1. Lack of user awareness about phishing techniques and scams [83502]
Impacts 1. The software failure incident led to a new and surprisingly simple phishing method affecting Google Chrome's mobile browser, targeting Android users [83502]. 2. Hackers were able to use a mixture of coding and screenshots to trick victims into giving up their private data, potentially leading to the theft of important information like passwords and credit card details [83502]. 3. The exploit known as the 'inception bar' trapped users in a 'scroll jail' within a fake page, making it difficult for users to access the legitimate address bar and detect the phishing attempt [83502]. 4. The phishing scam could potentially affect other browsers with similar features, not just Google Chrome, highlighting a broader impact on mobile browser security [83502].
Preventions 1. Implementing stricter validation checks for the display of SSL badges to prevent fake authentication indicators like in the 'inception bar' phishing scam [83502]. 2. Enhancing browser security measures to detect and prevent the manipulation of the address bar display, such as by restricting the ability of web pages to control the address bar behavior [83502]. 3. Educating users about common phishing tactics and encouraging vigilance when entering sensitive information on websites, especially when the URL bar behavior seems unusual [83502].
Fixes 1. Chrome could retain a small amount of screen space above, instead of giving up all the screen space to the web page, to signal that the URL bar is currently collapsed [83502].
References 1. Developer Jim Fisher's personal blog [83502] 2. Dailymail.com [83502] 3. Google [83502] 4. 9to5Google [83502]

Software Taxonomy of Faults

Category Option Rationale
Recurring multiple_organization (a) The software failure incident related to phishing using a fake address bar affecting Google Chrome's mobile browser has not been reported to have happened again within the same organization or with its products and services as per the provided article [83502]. (b) The article mentions that the phishing scam targeting Google Chrome on Android could potentially affect other browsers with similar features, indicating that similar incidents could potentially happen at other organizations or with their products and services [83502].
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase can be seen in the phishing scam affecting Google Chrome's mobile browser. Developer Jim Fisher discovered a new phishing method that tricks users by displaying a fake address bar and SSL badge, making a malicious page appear legitimate. This exploit involves a mixture of coding and screenshots to deceive users [83502]. (b) The software failure incident related to the operation phase is evident in how users can be trapped in a 'scroll jail' within the fake page created by the phishing scam. When users scroll using Google Chrome on Android, the address bar disappears, and attempts to scroll back up are futile as they are forced back down, unable to access the real address bar. This operation-related issue contributes to the success of the phishing scam [83502].
Boundary (Internal/External) within_system (a) within_system: The software failure incident described in the article is primarily within the system. The phishing scam targeting Google Chrome's mobile browser on Android devices is achieved through a manipulation of the address bar within the browser itself. Developer Jim Fisher demonstrated how hackers can trap users within a fake page by exploiting the behavior of the address bar disappearing when scrolling on Chrome for Android. This manipulation is done through coding and screenshots within the browser, indicating that the failure originates from within the system itself [83502]. (b) outside_system: There is no explicit mention in the article of the software failure incident being caused by contributing factors originating from outside the system. The focus of the incident is on the phishing scam exploiting vulnerabilities within the Google Chrome mobile browser on Android devices.
Nature (Human/Non-human) non-human_actions (a) The software failure incident in the article is primarily due to non-human actions. The phishing scam targeting Google Chrome's mobile browser on Android utilizes a deceptive technique involving a fake address bar that traps users within a 'scroll jail' on a malicious webpage. This exploit is achieved through a combination of coding and screenshots to create a convincing facade of a legitimate website, ultimately leading users to unknowingly disclose their private data [83502]. (b) The article does not provide specific information about the software failure incident being caused by human actions.
Dimension (Hardware/Software) software (a) The software failure incident related to hardware: - The article does not mention any hardware-related issues contributing to the software failure incident. Therefore, there is no information available regarding hardware-related factors in this incident [83502]. (b) The software failure incident related to software: - The software failure incident in this case is primarily due to a phishing scam that exploits a vulnerability in Google Chrome's mobile browser on Android. The scam involves using a fake address bar created through a combination of coding and screenshots to deceive users into giving up their private data. This indicates that the failure originated in the software itself, specifically in how the browser handles the display of the address bar and interacts with web pages [83502].
Objective (Malicious/Non-malicious) malicious (a) The objective of the software failure incident was malicious, as it involved a phishing scam targeting Google Chrome's mobile browser users. The scam utilized a fake address bar, SSL badge, and trapping users in a 'scroll jail' to deceive victims into giving up their private data, such as passwords and credit card information. The developer who discovered the exploit highlighted how scammers could use this technique to impersonate legitimate websites like HSBC Bank and steal important information from users [83502]. (b) The software failure incident was non-malicious in the sense that it was not caused by unintentional factors but rather by a deliberate phishing method designed to trick users and compromise their data security. The incident was a result of a sophisticated scam that involved a mixture of coding and screenshots to create a fake address bar and SSL badge, indicating a malicious intent to deceive users [83502].
Intent (Poor/Accidental Decisions) unknown (a) The intent of the software failure incident was not due to poor decisions but rather a deliberate phishing scam orchestrated by hackers targeting Google Chrome's mobile browser users [83502].
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to development incompetence is evident in the phishing scam affecting Google Chrome's mobile browser. Developer Jim Fisher discovered a new and surprisingly simple phishing method that tricks users into giving up their private data by using a fake address bar that displays the name of a legitimate website and an SSL badge, indicating the page is safe. Fisher demonstrated how scammers could camouflage a malicious webpage as a legitimate one, potentially stealing important information like passwords and credit card details [83502]. (b) The accidental aspect of the software failure incident is seen in how users can be trapped in a 'scroll jail' within the fake page created by the phishing scam. When users scroll using Google Chrome on Android, the address bar disappears, and Fisher found a way to trap users in this phony page, preventing them from accessing the real address bar even when trying to scroll back up. This accidental trapping of users within the deceptive page showcases a flaw in the browser's behavior that could lead to unintended consequences [83502].
Duration temporary (a) The software failure incident described in the article seems to be temporary. The phishing scam affecting Google Chrome's mobile browser is a result of specific circumstances introduced by the exploit discovered by developer Jim Fisher. The exploit involves a fake address bar that traps users in a 'scroll jail' within the browser, making it appear as if they are on a legitimate website when they are actually on a malicious page. This incident is not a permanent failure but rather a temporary issue caused by the specific phishing method utilized by hackers [83502].
Behaviour value, other (a) crash: The software failure incident described in the article does not involve a crash where the system loses state and stops performing its intended functions. (b) omission: The software failure incident does not involve the system omitting to perform its intended functions at an instance(s). (c) timing: The software failure incident does not involve the system performing its intended functions correctly, but too late or too early. (d) value: The software failure incident involves the system performing its intended functions incorrectly. Hackers use a phishing scam to trick users into giving up their private data by displaying a fake address bar and SSL badge to make a malicious page appear legitimate [83502]. (e) byzantine: The software failure incident does not involve the system behaving erroneously with inconsistent responses and interactions. (f) other: The software failure incident involves a deceptive behavior where the system displays a fake address bar and SSL badge to deceive users into thinking they are on a legitimate website, leading to potential data theft [83502].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence property, theoretical_consequence (a) unknown (b) unknown (c) unknown (d) People's material goods, money, or data was impacted due to the software failure as the phishing scam aimed to steal important information like passwords and credit card information from users [83502]. (e) unknown (f) unknown (g) unknown (h) Theoretical consequences discussed included the potential for scammers to camouflage a malicious web page as a legitimate one and steal important information from users [83502]. (i) unknown
Domain information (a) The software failure incident reported in the article is related to the information industry, specifically targeting users of Google Chrome on Android by using a phishing scam to trick victims into giving up their private data [83502].

Sources

Back to List