Google wants to make Chrome Extensions more secure - gHacks Tech News

Google wants to make Chrome Extensions more secure

Google announced a number of changes to Google Chrome's extensions system designed to make the use of extensions more secure.

The company has been in a constant battle against misuse of extensions that are either outright malicious or problematic from a privacy perspective.

Yesterday's announcement is the next step to make extension use securer. I reviewed the option to limit extensions with unlimited access to site data yesterday already. Chrome users may set extensions to "click to activate" or to a subset of sites they activate automatically starting with Chrome 70.

chrome extensions restrict access

Extension developers face a number of changes as well. Extensions that use obfuscated code are no longer allowed on the Store. Existing extensions that use code obfuscation have a grace period of 90 days while new extensions can't have any obfuscated code as they will be denied otherwise.

Google revealed that over 70% of malicious and policy violating extensions make use of code obfuscation, often to avoid detection by the Store's automatic scans to detect malicious or problematic extensions.

The change does not affect minification efforts to reduce the size of code. Minification techniques that are still allowed include removal of whitespace or code comments, or the shortening of variables and functions.

Existing extensions that are offered in Store at the time have 90 days to upload extension code that is not obfuscated. Extensions that fail to meet the deadline will be removed from the Chrome Web Store as a consequence.

Another change that affects extension developers directly is that developers need to enable 2-step verification for developer accounts in 2019.

Criminals have tried (and succeeded) in gaining access to developer accounts in the past to hijack accounts and push out extension updates that introduce malicious or problematic code

The third and final change affects the review process. Chrome extensions are reviewed automatically when a developer submits them. While automation is cost-efficient, it does not offer 100% protection against malicious extensions as the past has shown.

Extensions "that request powerful permissions" will have to pass "additional compliance" reviews and extensions that "use remotely hosted code" will be monitored closely.

Google plans to release an updated Manifest for extensions in 2019 "to create stronger security, privacy, and performance guarantees". Key goals include giving users additional mechanisms to control extension permissions, APIs that are "more narrowly-scoped", and introduction of new capabilities.

Closing Words

Google is finally doing something about malware and problematic extensions in the Chrome Web Store. Banning extensions with obfuscated code is a welcome step and so is the additional monitoring and review steps for some extensions.

My personal favorite is the ability to restrict where extensions can run that are designed to run on all pages.

Now You: Do you think the changes are enough to make the Chrome Web Store cleaner?

Summary
Google wants to make Chrome Extensions more secure
Article Name
Google wants to make Chrome Extensions more secure
Description
Google announced a number of changes to Google Chrome's extensions system designed to make the use of extensions more secure.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:


Previous Post: «
Next Post: »

Comments

  1. Nancy H. said on October 2, 2018 at 12:30 pm
    Reply

    Google gives me the creeps.

    1. ShintoPlasm said on October 2, 2018 at 10:01 pm
      Reply

      Why?

  2. Anonee said on October 2, 2018 at 12:56 pm
    Reply

    Sad that is has taken until the 10th anniversary of Chrome to finally implement these changes, but I guess better late than never…

  3. Emanon said on October 2, 2018 at 9:11 pm
    Reply

    This is all talk until it’s implemented and properly enforced.

  4. ShintoPlasm said on October 2, 2018 at 9:32 pm
    Reply

    Mozilla: removing manual code reviews for all extensions.
    Google: reinstating manual code reviews for prioritised extensions.

  5. John Fenderson said on October 2, 2018 at 9:46 pm
    Reply

    None of Google’s security efforts mean a thing to me until Google wants to make it more secure from Google.

  6. Future said on October 3, 2018 at 10:13 am
    Reply

    Yet another step to moving all into sandbox and restrict third party access to shared data.
    Welcome to the AMP controlled web, fully controlled local apps and all users data
    by one private company.

  7. Jozsef said on October 3, 2018 at 10:54 am
    Reply

    The day will never dawn when I install Chrome but since Vivaldi and Chromium use the same extensions, the net result is that I don’t even think of using any but Ublock Origin for the simple reason that I have no idea what else in the store is secure. When trusted sources like yourself tell us something is safe and maybe someday even the whole store, then I will look at these things.

    The fact is that Vivaldi for me has no glaring shortcomings that require additional functionality so I haven’t looked for any trusted reviews of extensions.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.