Sunday, February 9, 2025
HomeChromeGoogle to Block Logins From Embedded Browser Frameworks to Protect From Phishing...

Google to Block Logins From Embedded Browser Frameworks to Protect From Phishing & MitM Attacks

Published on

SIEM as a Service

Follow Us on Google News

Google announced a new security update to block users sign-in using Embedded browser frameworks in order to improve the protection against Phishing and MitM attacks.

Jonathan Skelker, Product Manager and Account Security at Google said,
“Form of phishing, known as “man in the middle” (MITM), is hard to detect when an embedded browser framework (e.g., Chromium Embedded Framework – CEF) or another automation platform is being used for authentication. “

Cybercriminals abusing this technology to perform Man-in-the-Middle attacks and steal the user’s credentials by intercepting the web traffic when Embedded browsers frameworks help users for the automated login process.

Embedded Browser Frameworks Lets Hackers Intercept the Traffic

If any users enter the Google account credentials on the phishing page that using Embedded browser frameworks will automate the login process by interacting with the original Google server.

Meanwhile, MITM attacker intercepts the communications between a user and Google in real-time to obtain the user’s credentials, and also this technique also used to bypass the 2-factor authentication.

Because we can’t differentiate between a legitimate sign in and a MITM attack on these platforms, we will be blocking sign-ins from embedded browser frameworks starting in June, Google said.

To prevent users from login based attacks, last year Google announced JavaScript to be enabled is require in your browser when users sign in so that Google can run a risk assessment whenever credentials are entered on a sign-in page and block the sign-in if we suspect an attack.

Similarly this new announcement brings more protection from credentials based phishing and Man-in-the-Middle attacks.

As an alternative method to embedded browser frameworks, Google suggested that developers use browser-based OAuth authentication, which enables users to see the full URL of the page where they’re entering their credentials.

“If you are a developer with an app that requires access to Google Account data, switch to using browser-based OAuth authentication today.”
Jonathan Skelker said.

You can follow us on LinkedinTwitterFacebook for daily Cybersecurity updates also you can take the Best Cybersecurity courses online to keep your self-updated.

Miner Malware Uses Multiple Propagation Methods to Infect Windows Machines and to Drop Monero Miner

Two Hackers of Bayrob Malware Gang Convicted for Infecting more than 400,000 Computers Worldwide


Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...