• Home
  • More…
  • Archives
  • About…

NUKLEOS weblog

Virtual Memory (Resurrected)

Feeds:
Posts
Comments
« 2020 Was A Good Year For Our Photovoltaics
January 6, 2021 – A Subject For Deep Study »

A Once Great Chrome Extension Has Become A Security Risk – Get Rid Of It!

08/01/2021 by Wouter

You will have to read the original Github ticket – or one of its copies, in case the Github ticket were to be closed/deleted/… –  but the essence of the message is that Chrome extension “The Great Suspender” (TGS) has become a very suspect suspender. According to the ticket, version 7.18 in the Chrome Web Store does not correspond to the source on Github, and has been modified in such a way that it could (can/will/…?) be used to invisibly execute tracking or malicious code!

Copy of a tweet urging to delete TGS from your computer

I was a great fan of that extension: I’m always juggling reading material and lots of browser-based applications at the same time, and that extension made it possible to keep them all open yet limit the memory and CPU footprint of Chrome to more reasonable sizes. I read about the trouble yesterday, and did not hesitate to delete this extension from all my computers!

There is mention of a few alternatives to The Great Suspender; at least one of them is a copy of the latest “pure” version of  TGS. But at the moment it isn’t available at the Chrome Web Store and requires a bit of manipulation to get it installed properly: that’s not for everyone.

By the way: if the ticket mentioned above is too technical for you, hop over to Life Hacker or The Register get their take on the subject.

Anyway, the worst part of the whole story is that Google does not seem to be interested in doing what it should do, that being to kick the extension out of its Web Store, at least while investigating the matter. But so far there seems to have been no reply from them, even though several people, including me, reported the extensions as incompatible with the rules of the Chrome Web Store. In the words of The Register:

The Register asked Google whether it plans to implement any measures to help make it easier for people to understand who maintains Chrome extensions and to understand code changes that have been made. We’ve not heard back.

Advertisement

Share this:

  • Twitter
  • LinkedIn
  • Email

Like this:

Like Loading...

Related

Posted in Internet, Privacy and Security, Software |

  • January 2021
    M T W T F S S
     123
    45678910
    11121314151617
    18192021222324
    25262728293031
    « Dec   Feb »
  • Android Apple & Macintosh ColdFusion Content Management Design and Art Internet Java Linkrot! Linux Mobile Computing Motorcycles Patents, IP, Privacy and More PDA Personal Photography Python R1100S Science Social Media Society Software Software Development Technology Web Development Wiki

Create a free website or blog at WordPress.com.

WPThemes.


Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
  • Follow Following
    • NUKLEOS weblog
    • Join 147 other followers
    • Already have a WordPress.com account? Log in now.
    • NUKLEOS weblog
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Copy shortlink
    • Report this content
    • View post in Reader
    • Manage subscriptions
    • Collapse this bar
 

Loading Comments...
 

You must be logged in to post a comment.

    %d bloggers like this: