Cover Image for Google disables a well-known ad blocker for "security reasons".
Tue Oct 15 2024

Google disables a well-known ad blocker for "security reasons".

Google is enhancing the security of its Chrome browser and has announced that support for the uBlock Origin extension will soon end. What other application could be affected?

Google is planning to discontinue support for popular extensions in its Chrome browser, specifically those operating under the Manifest V2 framework, such as uBlock Origin. This decision has been driven by security and privacy concerns. Since August, the company has been warning users about this change, informing them that the transition to Manifest V3 is part of its efforts to better protect its users. According to Google, this update is essential for both Chrome and the Chrome Web Store to keep extensions aligned with new requirements, which could result in the deactivation of those that do not comply.

User backlash has been notable on social media. Among the critical voices, Tim Sweeney, founder of Epic Games, denounced in a post that Google is using its dominant control in the Windows browser market in an anti-competitive manner to consolidate its advertising monopoly, blocking tools designed to remove ads.

Additionally, SquareX pointed out on its account that, despite the tighter control involved in Manifest V3, attackers are still capable of creating malicious extensions. This represents a significant risk for over 30 million Chrome users, who could be exposed to intrusive ads while looking for alternatives to their favorite extensions.

Google has suggested other options like uBlock Origin Lite, Adblock Plus, Stands AdBlocker, and Ghostery Tracker & Ad Blocker for those accessing uBlock Origin. With the new Manifest V3, the company also promises to give users greater control over the actions that extensions can take by shifting background contexts to “service workers,” which will run only when necessary. This change will also prohibit the use of externally hosted code, which poses a security risk by allowing unreviewed code execution in extensions, limiting execution to JavaScript included in the extension package that will be subject to review by the Chrome Web Store.

So far, no official date has been set for the migration to this framework, although it is rumored to happen in the coming months.